reference

Pagination

Every list endpoint on /v1 (studios, sources, destinations) returns a page in one shape:

{
  "data": [ { "id": "…" }, { "id": "…" } ],
  "nextCursor": "c3R1ZGlvXzQy"
}
  • data — the items on this page, ordered by id ascending.
  • nextCursor — an opaque cursor for the next page. It is omitted when there are no more pages, so "the response has no nextCursor" is your end-of-list signal.

Paging through a full list

Pass the nextCursor from one response as the cursor query parameter on the next request. Repeat until a response comes back without a nextCursor.

# Page 1
curl -sS "https://api-dev.traxstreaming.live/v1/studios?limit=50" \
  -H "Authorization: Bearer sk_live_…"

# Page 2 — feed back the nextCursor you just received
curl -sS "https://api-dev.traxstreaming.live/v1/studios?limit=50&cursor=c3R1ZGlvXzQy" \
  -H "Authorization: Bearer sk_live_…"

A loop, in pseudocode:

cursor = null
loop:
  page = GET /v1/studios?limit=100  (+ &cursor=<cursor> if set)
  process(page.data)
  if page.nextCursor is absent: break
  cursor = page.nextCursor

Parameters

Query param Type Default Notes
limit integer 50 Items per page. Values above the maximum are clamped to it, not rejected. A non-numeric or < 1 value is a 400 invalid_request.
cursor string An opaque cursor from a prior response's nextCursor. An empty/absent cursor starts at the beginning. A malformed cursor is a 400 invalid_request (never a 500).

The maximum limit is 200. Ask for more and you get 200.

Why cursors, not page numbers

The API uses keyset (cursor) pagination keyed on the resource id, not offset/page=N pagination. Cursors are stable under inserts and deletes: if a new studio is created while you're paging, an offset would silently skip or repeat a row, whereas a keyset cursor keeps advancing past the last id you saw.

Treat the cursor as opaque — it's a base64url token whose contents are an implementation detail. Don't parse it, construct it, or persist it long-term; just echo back the nextCursor you were given.

See the per-endpoint parameters in the API reference.