hydra:next
attribute with the URI for the next page. The URI already includes the cursor attribute.
hydra:next
attribute. This URI will automatically include the cursor value for the next page.
hydra:previous
attribute in the JSON-LD response. It will contain the URI for the previous page, including the cursor value.
hydra:next
and hydra:previous
URIs to navigate through the paginated results, based on your requirements.
Accept: application/ld+json
or Content-Type: application/ld+json
.
By following these instructions, you can effectively navigate through the paginated results using the cursor values provided in the hydra:next
and hydra:previous
attributes, without the need to manually include the cursor in your requests. This simplifies the pagination process and enhances the usability of our API.
X-Pagination-Style
header with the value "cursor"
to enable cursor pagination. If not specified, the API will assume offset-based pagination.
hydra:totalItems
field by default. Retrieving the total count can be resource intensive and impact response times, especially for large datasets. However, if you need the hydra:totalItems
information, you can include an additional header in your request. Set the X-Pagination-Enable-Partial
header with the value 0
to indicate that the response should include extra information, including the hydra:totalItems
count. Please be aware that enabling this feature may impact API response times, as the backend needs to perform a count operation on the dataset.
hydra:totalItems
count, please consider the potential impact on API response times.
GET /taxpayers/{taxpayerId}/invoices
GET /taxpayers/{taxpayerId}/invoices/line-items
GET /taxpayers/{taxpayerId}/invoices/{invoiceId}/line-items
GET /invoices/{invoiceId}/line-items
GET /taxpayers/{taxpayerId}/invoices/payments