Pagination and filtering
Every list endpoint uses the same paging rules and the same response shape.
Response shape
A list endpoint returns the rows in a data array, with a pagination object:
{
"data": [],
"pagination": {
"page": 1,
"pageSize": 25,
"total": 42,
"totalPages": 2
}
}| Field | Type | Notes |
data | array | The rows for this page. |
pagination.page | number | The page you asked for. |
pagination.pageSize | number | The rows per page you asked for. |
pagination.total | number | The total number of matching rows. |
pagination.totalPages | number | The total number of pages. Always at least 1. |
Shared query parameters
| Parameter | Type | Default | Notes |
projectId | UUID | required | The project to read. |
page | integer | 1 | The page number, starting at 1. |
pageSize | integer | 25 | Rows per page. The minimum is 1. The maximum is 100. |
search | string | none | Free text search across the main fields. |
Filters
Each list has its own filters on top of the shared parameters. For example, testimonial submissions can be filtered by status, type, sentiment, minRating, formBuilderId, and customerId.
Some testimonial filters accept more than one value as a comma separated list, for example status=approved,pending.
See each list endpoint page for its full filter set.
Read every page
- Request
page=1. - Read
pagination.totalPages. - Request each page from 2 up to
totalPages. - Stop when
pagereachestotalPages.
Related pages
Was this helpful?