GitHub

GET /v1/github/activity

GitHub Activity API

List a GitHub user's recent public activity — pushes, issues, pull requests, and similar events.

~12 credits (0.4/result) per request

Try in Playground Get your API key — free Read the docs

TL;DR

List a GitHub user's recent public activity — pushes, issues, pull requests, and similar events. The GitHub Activity API (GitHub) is a single authenticated GET request to /v1/github/activity that responds with clean JSON and costs ~12 credits (0.4/result). Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.

What is the GitHub Activity API?

The GitHub Activity API lets you list items in bulk with metadata for GitHub activity with a single REST call. No OAuth, no infrastructure to maintain, and no platform SDKs — send the request, get clean structured JSON back. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh.

What you get

Bulk list of activity with metadata
Dates, URLs, and engagement fields when available
Configurable result limit
Ideal for monitoring and content pipelines

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

username*stringGitHub username or profile URL.limitoptionalintegerMax items to return (default 30, max 100). Billed per result.cursoroptionalstringPagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response.cacheoptionalbooleanSet true to serve from the 24h response cache. Default false — always fetch fresh data.

API keyoptionalPaste your key to get a ready-to-run snippet. It stays in your browser.Sign in to run live

curl "https://api.captapi.com/v1/github/activity?username=vercel" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "username": "torvalds",
    "totalReturned": 5,
    "nextCursor": "2",
    "hasMore": true,
    "events": [
      {
        "id": "15224705962",
        "type": "PushEvent",
        "repo": "torvalds/linux",
        "actor": "torvalds",
        "createdAt": "2026-07-18T04:53:40Z"
      },
      {
        "id": "15206866323",
        "type": "PushEvent",
        "repo": "torvalds/linux",
        "actor": "torvalds",
        "createdAt": "2026-07-17T20:16:14Z"
      },
      {
        "id": "15194982279",
        "type": "PushEvent",
        "repo": "torvalds/linux",
        "actor": "torvalds",
        "createdAt": "2026-07-17T16:32:53Z"
      },
      {
        "id": "15192887403",
        "type": "PushEvent",
        "repo": "torvalds/linux",
        "actor": "torvalds",
        "createdAt": "2026-07-17T15:58:02Z"
      },
      {
        "id": "15143452538",
        "type": "PushEvent",
        "repo": "torvalds/linux",
        "actor": "torvalds",
        "createdAt": "2026-07-16T23:58:05Z"
      }
    ]
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

usernameAccount username / handle.
totalReturnedNumber of items returned in this response.
nextCursorCursor to pass for the next page of results.
hasMoreWhether more results are available beyond this page. When true, pass nextCursor to fetch the next page.

Events

Each item in events contains:

idStable platform ID for the item.
typeContent type of the item.
repoRepo. Example: "torvalds/linux".
actorActor. Example: "torvalds".
createdAtCreation date (ISO 8601).

Parameters

Name	Type	Required	Description
username	string	Yes	GitHub username or profile URL.
limit	integer	No	Max items to return (default 30, max 100). Billed per result.
cursor	string	No	Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response.
cache	boolean	No	Set true to serve from the 24h response cache. Default false — always fetch fresh data.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs ~12 credits (0.4/result) — billed per result, so the exact amount scales with how many items you request. Pass cache=true for a free 24h cache hit; default is always fresh (metrics refresh within ~1 hour).

Using an AI agent? This endpoint is the MCP tool github_activity via @captapi/mcp. Set it up →

How it works

1. Sign up — get 100 free credits, no card required.
2. Create a key from your dashboard.
3. Send one request to /v1/github/activity and parse the JSON response.

Use cases

Content Pipelines

Ingest a channel's catalog in bulk.

Monitoring

Detect new uploads automatically.

Archiving

Snapshot a creator's full library.

Analytics

Aggregate performance across many videos.

Frequently asked questions

What does the GitHub Activity API do?+

The GitHub Activity API lets you list items in bulk with metadata from a public GitHub GitHub resource using one GET request to /v1/github/activity. It returns clean JSON — no OAuth or infrastructure setup required.

How many credits does the GitHub Activity API cost?+

At the default limit this endpoint costs 12 credits (0.4 per result). Billing scales with how many results you request. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh. Failed or empty results are never charged.

Do I need a GitHub API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.

Is the GitHub Activity API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh. Use it for analytics, monitoring, and content automation.

More GitHub APIs

GitHub User API GitHub Repositories API GitHub Pull Requests API GitHub Followers API GitHub Following API GitHub Contributions API GitHub Repository API GitHub Trending Repositories API GitHub Trending Developers API

Ready to use the GitHub Activity API?

Get started free