Pagination

List endpoints — such as GET /v1/catalog and GET /v1/orders — are cursor-paginated. Each response carries the page of results, whether more remain, and the cursor to fetch the next page:

{
  "data": [ /* ... */ ],
  "hasMore": true,
  "nextCursor": "MTc4NTg2MDczNzUyOTc5MTAwMDo1NzJlMjRjNi0yNzBlLTQ2YTAtOWI4NS1lZGQ3ZWViNTI5MGU"
}

To fetch the next page, pass nextCursor back as the cursor query parameter:

curl "https://api.sodacards.com/v1/orders?limit=1&cursor=MTc4NTg2MDczNzUyOTc5MTAwMDo1NzJlMjRjNi0yNzBlLTQ2YTAtOWI4NS1lZGQ3ZWViNTI5MGU" \
  -H "X-API-Key: sc_test_your_key_here"

Stop when hasMore is false (nextCursor is empty on the last page).

limit bounds the page size; it is clamped to a sane maximum.
The cursor is opaque — do not parse or construct it. Pass back exactly what you received. A malformed cursor is refused with invalid_cursor.
Cursors are keyset-based, so paging stays correct even as new records arrive.

Get started

Core concepts

Webhooks

Reference