Pagination & Filtering
All list endpoints in the Strictly API support pagination and filtering via query parameters. Understanding these parameters helps you avoid timeouts, retrieve complete datasets, and build efficient integrations.
Default behavior
If you omit pagination parameters, the API returns the first 10 records. For most production use cases you will want to control this explicitly.
Pagination parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
page | integer | 1 | Page number (1-based) |
limit | integer | 10 | Number of records per page |
Get first 50 records
Get page 2 (records 11–20 at default limit)
Get page 3 with 25 records per page
Never rely on the default limit of 10 in your application logic. Always pass page and limit
explicitly so your code is resilient to data growth.
Sorting
Use the sort parameter to control result order. Prefix the field name with - for descending
order (most recent first):
| Example | Result |
|---|---|
sort=transactions.transactionAt | Ascending (oldest first) |
sort=-transactions.transactionAt | Descending (newest first) |
Most recent transactions first
Date range filtering
Many endpoints accept startDay and endDay to filter records by a time window.
Format
Both parameters use ISO 8601 format: YYYY-MM-DDTHH:mm:ss.SSSZ
| Example | Represents |
|---|---|
2025-03-03T05:00:00.000Z | March 3, 2025 at 5:00 AM UTC |
2025-03-06T04:59:59.999Z | March 6, 2025 at 4:59:59.999 AM UTC |
The Z suffix means UTC. To query for "all of March 3rd in Eastern Time" (UTC-5), start at
2025-03-03T05:00:00.000Z (midnight ET = 5 AM UTC) and end at 2025-03-04T04:59:59.999Z.
Use the timezone parameter as an alternative — see below.
Timezone parameter
The timezone parameter adjusts filtering to a named timezone so you don't have to manually
calculate UTC offsets:
Code
Accepted values follow the IANA timezone database, for example:
America/New_YorkAmerica/ChicagoAmerica/Los_AngelesAmerica/DenverUTC
Full example
This request retrieves the 10 most recent transactions within a 3-day window, sorted by date, in Eastern Time:
cURL
JavaScript
Best practices
- Always set
pageandlimitexplicitly to prevent silent data truncation at 10 records - Sort by date descending (
sort=-transactions.transactionAt) to get recent records first when building dashboards or activity feeds - Use
timezoneinstead of manually converting UTC offsets — it's less error-prone - Page through all results in batch jobs rather than raising
limitto extreme values, which can cause timeouts on large datasets
Which endpoints support pagination?
Pagination (page, limit, sort) is supported on all list (GET) endpoints, including:
GET /public/customerGET /public/transactionsGET /public/planGET /public/subscriptionGET /public/invoiceGET /public/payment-linkGET /public/report/pivot
Date range filtering (startDay, endDay, timezone) is supported on transaction and report
endpoints. See the API Reference for the full parameter list per endpoint.