Choose the next page.
The response gives data, count, dataset_id, dataset_version, request_id, next_cursor and meta. A null cursor means this query has no next page. A non-null cursor is opaque: do not decode, edit or reuse it with different filters.
For HTTP, repeat the exact request from the HTTP and Python guide and add --data-urlencode "cursor=$ORIGINFOLD_NEXT_CURSOR", where the variable contains the preceding response's next_cursor. Keep the version, fields, identifiers, date range, cutoff and page size unchanged.
from dataclasses import replace
# Continue from the query and page in the HTTP and Python guide. This requests at most one more page.
with Client.from_env() as client:
if page.next_cursor is not None:
next_page = client.query(replace(query, cursor=page.next_cursor))
print(next_page.data)Each successful page is charged to the same account usage as the Explorer. There is no automatic pagination, export or download_all. If a cursor is invalid after an access or version change, inspect the current catalogue and start a new query deliberately.
Keep a query, not its results
In the Explorer, name a query and choose Save query. Up to 50 bounded definitions can be retained. Opening a saved definition or refreshing usage does not run it. Run query and Load next page each request data. Saved definitions remain when access ends; running them still requires current access. Results, API keys and cursors are not saved.