GET /api/v2/requests
Allowed for
- End Users
Pagination
- Cursor pagination (recommended)
- Offset pagination
See Pagination.
High volume requests
Requesting a large number of tickets may return intermittent "503 Service Unavailable" errors. Workarounds:
- Use cursor pagination with a smaller page size. Example: GET /api/v2/requests?page[size]=100. If you continue to see timeouts, try a smaller value, such as 50 or 25.
- Use Search Requests instead.
Servers
- https://{subdomain}.{domain}.com
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
page |
No |
Pagination parameter. Supports both traditional offset and cursor-based pagination:
These are mutually exclusive - use one format or the other, not both. |
|
sort_order |
String | No |
One of "asc", "desc". Defaults to "asc" |
per_page |
Integer | No |
Number of records to return per page. Note: Default and maximum values vary by endpoint. Check endpoint-specific documentation for limits. |
sort_by |
String | No |
Possible values are "updated_at", "created_at" |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.