Pagination
Using page tokens to navigate subsets of results.
Many Veza endpoints return pages of results by default, or are paginated when setting the page_size
query parameter.
When making API requests that return multiple items, the response will include the following pagination-related fields:
has_more
: A boolean indicating whether there are additional results availablenext_page_token
: A token that can be used to retrieve the next page of results
To get the next page of results, use the value returned by next_page_token
to set the page_token
query parameter for the next page of results.
When implementing pagination, you must rely on the
has_more
field to determine if there are additional results available. Veza APIs may return a non-emptynext_page_token
even when there are no more results available.
Set the maximum number of results per page and the page to begin returning results with
page_size
(maximum 100) andpage_token
:POST /api/v1/assessments/query_spec:nodes?page_size=10&page_token=Na%3D%3D
Responses with more than one page will contain
"has_more": "true"
and include thenext_page_token
string.A page can be empty even when more results exist. Always check the
has_more
field in the response to verify if additional results exist.The
page_token
query parameter must be URL-encoded in POST requests (replacing non-alphanumeric characters). You can achieve this with theurllib.parse.urlencode
python function or another utility.
Sample Request
Sample response
Last updated