API Pagination Inspector
Paste an API JSON response and, optionally, its HTTP Link header. The inspector looks for likely next-page URLs, cursor tokens, page/offset metadata and result arrays—then gives you a starter pagination loop in JavaScript or Python.
Inspect an API response
Paste the response body exactly as JSON. If you have response headers, paste the value of the Link header below. This tool analyzes your sample only; it does not fetch URLs.
Pagination code starter
After analysis, choose a language and copy the example. Review the item path, authentication headers, rate limits and stop condition for your specific API.
// Run Analyze response to generate a pagination starter.
# Run Analyze response to generate a pagination starter.
What is API pagination?
API pagination splits a large collection into smaller responses called pages. Instead of returning thousands of records at once, an endpoint returns a smaller batch and provides a way to request the next batch. The next-page signal may be an HTTP Link header, a cursor token in JSON, or page/offset metadata.
Pagination formats this inspector looks for
1. Link header pagination
Some APIs return an HTTP Link header containing one or more related URLs. A link marked rel="next" identifies the next page. GitHub's REST API documentation shows this pattern. The format is standardized by the Web Linking specification, RFC 8288.
2. Cursor-based pagination
Cursor APIs use a token that points to a position in a result set. Common names include next_cursor, nextCursor, end_cursor and starting_after. Some APIs also return a boolean such as has_more. The exact request parameter and termination behavior are API-specific.
3. Page or offset pagination
Page-based APIs may return values such as page, current_page, total_pages, offset, limit or per_page. The response may include a total count or a next-page field. A page number alone does not prove that another page exists.
How to use the API pagination checker
- Call the API using your own client, command line or API tool.
- Copy the JSON response body into the first field.
- If available, copy the HTTP
Linkheader value into the second field. - Select Analyze response and review the detected fields and likely pagination pattern.
- Copy the JavaScript or Python starter, then adapt it to the API's documented request parameter and response shape.
What the detector can and cannot tell you
The inspector searches a bounded set of common field names and nested JSON paths. It can point out likely pagination metadata, arrays and next links, but it cannot prove that a field is used for pagination. A field named next could be unrelated application data. Some APIs expose pagination only in response headers that are not included in the JSON body. The inspector therefore reports evidence and a likely pattern, not a guaranteed API specification.
For safety and privacy, the page does not send a request to a user-supplied URL and does not upload the pasted payload. Do not paste credentials, access tokens or personal data into public websites.
Official references
Frequently asked questions
Can this tool call my API endpoint?
No. It only inspects JSON and header text that you paste. This keeps it backend-free and avoids CORS restrictions or accidental requests to private endpoints.
How can I tell whether an API uses cursor or offset pagination?
Look for response fields and documented request parameters. Cursor clues include cursor tokens such as next_cursor or end_cursor. Offset clues include page, offset, limit and total_pages. The detector uses these names as heuristics; the API documentation is authoritative.
What does rel="next" mean in a Link header?
It labels a related link as the next resource in a navigation sequence. The next-page URL is carried in angle brackets, followed by a relation parameter such as rel="next".
Why did the inspector not find pagination?
The API may use uncommon field names, place metadata in HTTP headers you did not paste, or return all results in one response. The detector intentionally uses common patterns and does not claim that an API is unpaginated when it finds none.
Does the generated code work for every API?
No. It is a starting point. You must adapt authentication, the result-array path, pagination parameter, rate-limit handling and API-specific stop condition.
About NewTechie: This free API pagination inspector runs locally in your browser. It does not connect to an API or upload your pasted response.