Skip to main content
List endpoints are cursor-paginated. Every paginated response carries a nextCursor:
  1. Make the first request without cursor.
  2. If the response has a nextCursor, pass it back as the cursor query parameter, with exactly the same filters, to get the next page.
  3. Stop when nextCursor is absent or null.

Rules

  • Treat cursors as opaque. Never build, parse, or modify one. Some endpoints use strings and others use numbers, and the format can change.
  • A cursor belongs to one query. Reusing a cursor with different filters doesn’t always fail. It can silently skip or repeat rows. When the query changes, start again without cursor.
  • Pages can be short or empty before the end, for example when items become unavailable between pages. Keep going while nextCursor is present.
  • Results are live, not a snapshot. Items added during a walk may appear on your next full pass.

Page sizes

On the Recruiter API, a limit above the maximum is lowered to the maximum. On the Agency API, it’s rejected with 400. GET /recruiter/recommendations isn’t paginated: it returns up to 20 results (limit, default 20).