Developer

Get a GitHub user's contribution graph · GitHub API

GET/github/users/{username}/contributions
$min $0.003

Returns a GitHub user's daily contribution counts and total for one calendar year (default: the current year). Returns `not_found` when the user does not exist.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/github/users/{username}/contributions \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

usernamepathrequired
GitHub username of a user or organization.
yearquery
Calendar year for the contribution graph. Default: current calendar year.
The parameter for this GitHub operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the GitHub API in the developer category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs GitHub public data alongside Hacker News, social or web data, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Resolve a public GitHub identity into structured profile metadata for enrichment agents.
  • Refresh creator, company, or account snapshots without managing source-specific response shapes.
  • Give an AI agent a stable GitHub data source without building a per-platform integration.
  • Normalize GitHub responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful Get a GitHub user's contribution graph call returns data as an array; each record carries these fields.

datestring | null
Calendar date for this cell (YYYY-MM-DD).
contribution_countnumber | null
Number of contributions on this day.
colorstring | null
Heatmap cell color when provided.
intensitynumber | null
Contribution intensity level for the heatmap cell.