GitHub contribution calendar API
The public contribution graph for one year: the total and a count per day.
100 free credits. No card needed.
torvalds, 2025
Sent with a handle and the year
- Cost
- 1 credit
- Fields
- 6
- Cached
- 30 days
One contribution calendar a request
What you get in each contribution calendar
What you can build with it
How active a developer is. total gives a year's contributions, 2,925 for torvalds in 2025, and days gives the count for each date, for a calendar or a trend line.
- handle
- torvalds
- total
- 2,925
Busy days and quiet weeks. Each day carries its own count, so streaks, gaps and the busiest weeks fall out of one call. The sample's third day of 2025 has 11.
- 2025-01-01
- 1
- 2025-01-02
- 2
- 2025-01-03
- 11
From a key to JSON.
handle (torvalds) and year (2025).data.The request. GET /v1/github/user/contributions
curl -G "https://api.socialscrape.dev/v1/github/user/contributions" \ -d handle=torvalds \ -d year=2025 \ -H "x-api-key: $SOCIALSCRAPE_API_KEY"
import requests r = requests.get( "https://api.socialscrape.dev/v1/github/user/contributions", params={"handle": "torvalds", "year": "2025"}, headers={"x-api-key": KEY}, ) contribution_calendar = r.json()["data"]
const url = new URL("https://api.socialscrape.dev/v1/github/user/contributions"); url.searchParams.set("handle", "torvalds"); url.searchParams.set("year", "2025"); const res = await fetch(url, { headers: { "x-api-key": KEY }, }); const { data } = await res.json();
The response. A sample, in the shape every call returns.
{
"ok": true,
"credits_charged": 1,
"data": {
"handle": "torvalds",
"total": 2925,
"days": [ ..., ..., ... ]
}
}
Ask in plain words. Ask your agent for GitHub contribution calendar in plain words, and the SocialScrape MCP server makes the call.
Get the contribution calendar for torvalds.
Here is the contribution calendar: "@torvalds", with 2,925 total.
One tool call
GitHub contribution calendar, given a handle.
Same price as the API
1 credit a call; a repeat within 30 days is free.
Runs on your machine
Your key stays in your agent's settings.
Pay only for data you get.
Failed requests and cached repeats are free.
1,000 credits
$13 one time
Get an API key- $13.00 per 1,000 credits
- Credits never expire
- No subscription
25,000 credits
$55 one time
Get an API key- $2.20 per 1,000 credits
- Credits never expire
- No subscription
230,000 credits
$349 one time
Get an API key- $1.52 per 1,000 credits
- Credits never expire
- No subscription
Questions, answered.
Common questions
What does intensity_by_date hold?
The shade GitHub gives each day on its graph, a level rather than a count: 2 for the sample's day with 11 contributions. Read days for the counts.
Which years can I ask GitHub contributions for?
Any calendar year from 2008 on, as year. Leave it out for the current year.
How do I compare a developer's years?
Call it once for each year and set the totals side by side, or line up the daily counts week by week.
What did the contributions consist of?
GitHub user activity says what the work was, month by month, and in which repositories.
What does it return?
The contribution calendar has up to 6 fields, and the sample fills handle, total and days.
What do I send?
Send one of handle or url.
handle: A username (with or without @) or a profile or repository URL (github.com/<name>).
url: Profile URL (github.com/<user>).
year: Calendar year (2008 onward); default the current year. From 2008 to 2100.
Which errors can it return?
invalid_params, unsupported_url and not_found. None is charged, and the errors list says which to retry.
Is there an SDK call for it?
client.github.user_contributions(...) in Python and client.github.userContributions() in TypeScript.
Start pulling social data.
100 free credits. No card needed.