Protocols
Saved & recent

Pagination

Also called: paged results, continuation token

Pagination divides a collection response into smaller pages. An API may use page numbers, offsets, continuation tokens or links to navigate them. This is an API design pattern, not one universal HTTP protocol: callers must follow the service’s documented ordering, parameters and rules for detecting the end.

For example, a catalogue returns twenty results plus an opaque continuation token. The client sends that token back with the same filters to request the next batch, without interpreting its contents. Another API may provide a Link header with rel="next". A continuation token is a navigation handle, not permission to read records; authorization still applies to every request.

Read first
HTTP
Related
REST, HTTP headers, OpenAPI
Further reading
first request filter=books · page_size=20 second request filter=books · page_size=20 page_token=<opaque> authorization check authorization check catalogue page 1 catalogue page 2 first response next=<opaque> final response no next token opaque continuation token example token convention
This example returns twenty results, then seven final results. The next request returns T1 unchanged, preserves the query, and passes authorization again. The token is a navigation handle, not a credential.

View in the full Protocols collection