GET /api/v2/suspended_tickets
Allowed For
- Admins and agents in custom roles with permission to manage suspended tickets on Enterprise plans
- Unrestricted agents on all other plans
Sorting
You can sort the tickets with the sort_by and sort_order query string parameters.
Pagination
- Cursor pagination
See Pagination.
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 |
The order in which to sort the suspended tickets. This can take value |
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 |
The field to sort the suspended tickets by. One of "author_email", "cause", "created_at", or "subject" |
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.