Pagination

List endpoints use opaque cursors, not page numbers.

GET /events and GET /orders return one page at a time and a cursor for the next page.

The loop

1. Make the first request without cursor.
2. If the response has a next_cursor, pass it unchanged as cursor on the next request, with the same filters.
3. Stop when there is no next cursor.

The two lists signal the last page slightly differently:

	Events	Orders
Default limit	20	25
Allowed limit	1 to 50. Larger values are clamped to 50.	1 to 100. Out of range is 400.
Last page	next_cursor is absent and has_more is false	next_cursor is null

Write your loop to stop on “no usable cursor” and it handles both:

Node

async function listAll(path, key) {
  const items = [];
  let cursor;
  do {
    const url = new URL(`${BASE}${path}`);
    url.searchParams.set("limit", "50");
    if (cursor) url.searchParams.set("cursor", cursor);
    const res = await fetch(url, { headers: { Authorization: `Bearer ${token}` } });
    const { data } = await res.json();
    items.push(...data[key]);
    cursor = data.next_cursor; // undefined or null on the last page
  } while (cursor);
  return items;
}

const events = await listAll("/events", "events");

Cursor rules

• Cursors are opaque. Do not parse, build or modify them.
• Reuse a cursor only with the filters that produced it. Changing event_id or status mid-loop gives you a page you didn’t ask for.
• A malformed cursor is 400: invalid_cursor on events (also for a cursor from another organization), validation_failed on orders.
• Cursors are for walking a list now, not bookmarks to keep for later.