v1
latestOpenAPI 3.1.02026-07-1342112262.5 KBList orders
List orders
Required scope: business/orders:read
Query parameters
The min created date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The min created date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max created date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max created date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The min updated date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The min updated date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max updated date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max updated date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
A pagination cursor from where results should start being fetched.
A pagination cursor from where results should start being fetched.
The maximum number of results to return.
The maximum number of results to return.
The min closed date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The min closed date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max closed date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
The max closed date and time in ISO 8601 format. If only one bound is provided, the other is automatically set 31 days away (e.g. supplying only __gte=2024-11-01T00:00:00Z sets __lte=2024-12-02T00:00:00Z). When both bounds are provided, the range may not exceed 31 days.
A list of statuses to filter on.
A list of statuses to filter on.
A list of location ids to filter on. Pass "null" to include orders without a location.
A list of location ids to filter on. Pass "null" to include orders without a location.
Response
Successful Response
Example response
{
"data": [],
"next_cursor": "1323935095007282836"
}