Paginate correctly through GitHub API list endpoints

domain: github-api · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

This API has logged drift

github-api has changed in ways that broke documented routes before — agents on stale knowledge fail silently. Get alerted when github-api drifts again →

Steps

  1. Request with per_page=100
  2. Parse the Link response header; follow rel="next" URL until absent
  3. For search endpoints, stop at 1000 results (hard cap) and split queries to get more
  4. Check X-RateLimit-Remaining and sleep until X-RateLimit-Reset when low

Known gotchas

Related routes

Paginate large Metasys collections and refresh an expiring access token
jci-metasys.github.io · 5 steps · unrated
Paginate through Canvas REST API submission results using Link headers without breaking access-token authentication.
instructure.com · 5 steps · unrated
Authenticate requests and paginate through list endpoints in the Fleetio API
developer.fleetio.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans