Pagination - Asset API Documentation

Most Asset API endpoints that return lists of objects support pagination, allowing you to retrieve data in smaller chunks. Asset uses cursor-based pagination, which ensures no records are skipped between pages and provides better performance than offset-based pagination.

Paginating Through Records

When an endpoint supports pagination, the API response includes pagination tokens:

{
  "next_page_token": "xK8QZ5JpT0L4FzDc6VaRb1MNhgAAAAABk9cXz3G2hJn7Yx2K1Nv==",
  "previous_page_token": "pT0L4FzDc6VaRb1MNhxK8QZ5JgAAAAABk9cXz3G2hJn7Yx2K1Nv==",
  "records": []
}

Use next_page_token to request the next page.
Use previous_page_token to request the previous page.
If either token is null, there are no additional pages in that direction.

To retrieve the next page, include the page_token parameter in your request:

curl --request GET \
  --url "https://api.asset.com/v0/business?page_token=<next_page_token>" \
  --header "Authorization: Bearer <token>"

To request the previous page:

curl --request GET \
  --url "https://api.asset.com/v0/business?page_token=<previous_page_token>" \
  --header "Authorization: Bearer <token>"

Page Size

By default, the API returns 50 records per page, with a maximum of 100 records per page. You can adjust this by setting the page_size parameter:

curl --request GET \
--url 'https://api.asset.com/v0/business?page_token=<next_page_token>&page_size=100' \
--header 'Authorization: Bearer <token>'

Questions? Reach out via our Contact form.

⌘I

​Paginating Through Records

​Page Size

Paginating Through Records

Page Size