Paginating results with cursors

List endpoints return at most a page of records at a time. To get the next page, you follow a cursor rather than incrementing an offset. Cursor pagination is stable: new filings arriving mid-walk will not shift or duplicate rows you already fetched.

How it works

Each response includes a next_cursor when more results exist. Pass it back as the cursor query parameter to fetch the following page. When next_cursor is null, you have reached the end.

GET /v1/licenses?county=Miami-Dade&limit=100
# response: { "data": [...], "next_cursor": "c_8f21a" }

GET /v1/licenses?county=Miami-Dade&limit=100&cursor=c_8f21a

Best practices

• Keep your filters identical across every page of the same walk — changing them invalidates the cursor.
• Store the last cursor you successfully processed so you can resume after a crash.
• Do not try to construct cursors yourself; treat them as opaque strings.