Skip to main content
Three list endpoints page through results with a cursor:
  • GET /requests
  • GET /opportunities
  • GET /introductions
Every response from a paginated endpoint has the same envelope:

​
Reading a page

Pass limit to control page size. It is an integer from 1 to 100, and the default is 30:
meta.nextCursor is the token for the next page. Pass it back as cursor:
meta.nextCursor is null on the last page. That is the only end-of-list signal. The response has no total count.
A cursor is valid only for the exact list and filters that produced it. Reusing one with a different status or side filter fails with invalid_cursor. Restart pagination without a cursor.

​
Endpoints without pagination

GET /radar/nodes and GET /radar/submissions return their full result in data, with no meta and no cursor.

Rate limits

How many requests you can make while paging through a large list.

Errors

invalid_cursor and every other error code.