GET /api/v2/tickets/{ticket_id}/audits

Lists the audits for a specified ticket.

Pagination

Cursor pagination (recommended)
Offset pagination

See Pagination.

Returns a maximum of 100 records per page.

Note: Audits for Archived Tickets do not support pagination for this endpoint.

Allowed for

Agents

Servers

https://{subdomain}.{domain}.com

Path parameters

Name	Type	Required	Description
`ticket_id`	Integer	Yes	The ID of the ticket

Query parameters

Name	Type	Required	Description
`page`		No	Pagination parameter. Supports both traditional offset and cursor-based pagination: Traditional: `?page=2` (integer page number) Cursor: `?page[size]=50&page[after]=cursor` (deepObject with size, after, before) These are mutually exclusive - use one format or the other, not both.
`include_boundary_indicators`	Boolean	No	When true, includes `has_more` indicator in the cursor pagination response meta. Only valid with cursor pagination (page[size], page[after], page[before]).
`sort_order`	String	No	Sort order. Defaults to "asc" Valid values: `"desc"` `"asc"`
`include`	String	No	A comma-separated list of sideloads to include in the response.
`filter_events[]`	Array	No	Filter audit events by type. Use the format `filter_events[]=Type1&filter_events[]=Type2`.
`sort`	String	No	Field to sort results by. Prefix with `-` for descending order. When used with cursor pagination, this determines the cursor ordering. Example: `?sort=name` or `?sort=-created_at`
`include_item_cursors`	Boolean	No	When true, includes cursor values for each item in the cursor pagination response. Only valid with cursor pagination (page[size], page[after], page[before]).

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.