Solved Docs

Pagination

The cursor model for list endpoints.

List endpoints use cursors, not page numbers:

GET /v1/links?limit=50&cursor=c_eyJrIjoiMjAyNi0xMC0wMVQxMjowMDowMFoiLCJpZCI6Imxua18wMUo5In0
{ "items": [ /* … */ ], "next_cursor": "c_eyJrIjoi…", "has_more": true }

Pass next_cursor straight back in as cursor to get the next page; next_cursor: null means you're on the last page. limit defaults to 50 and caps at 100 (some export-style endpoints allow more — see that endpoint's docs). Lists sort newest-first (created_at, immutable) unless the endpoint says otherwise — sorting by something that can change under you (like click count) would break the cursor, so those are separate "top N" endpoints without pagination at all.

Treat the cursor as opaque — don't parse it, don't construct one by hand. If a request's filters change between pages, you'll get 400 cursor_invalid; start over from an unfiltered call.

Next: Errors · Rate limits