GET /api/v2/users/{user_id}/tickets/requested
List User Requested TicketsServers
- https://{subdomain}.{domain}.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
user_id |
Integer | Yes |
The id of the user |
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 |
Sort order. Defaults to "asc" Valid values:
|
include |
String | No |
Sideloads to include in the response. Accepts a comma-separated list of values. See Sideloading. |
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. |
exclude_archived |
Boolean | No |
If true, excludes archived tickets from the results. |
exclude_count |
Boolean | No |
If true, excludes the total count from the results. |
sort_by |
String | No |
Sort by Valid values:
|
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.