get_ticket_audits
Read-onlyIdempotent
Retrieve the audit history of a Zendesk ticket to trace state changes, identify rule attributions, and debug unexpected macro or trigger behavior.
Instructions
Returns the audit history for a ticket, every state change with rule attribution and event timestamps. Defaults to limit: 100 events; pass since to bound by date, event_types: ["Change"] to skip Comment events entirely (much smaller response). Scope-gated, requires config_plus_audits or full; at config_plus_audits Comment-event bodies are auto-redacted. Use this for forensic debugging ("why did this macro send the ticket to the wrong group?"), via.source on each audit names the trigger / macro / app that made the change. For pure timing data, get_ticket_metrics is cheaper.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Ticket ID | |
| limit | No | Max audit events to return. Default 100. Audits on noisy tickets can run to thousands of events. | |
| since | No | ISO timestamp. Only return audits with created_at >= since. Useful for "what changed today" queries. | |
| cursor | No | ||
| fields | No | ||
| filter | No | ||
| refresh | No | Bypass cache and re-fetch from Zendesk | |
| verbose | No | Return full audit objects instead of the thin projection | |
| instance | No | Override the sticky instance for this call | |
| event_types | No | Filter audit.events to only these types. Common: ["Change"] to skip Comment events entirely. ["Change","Notification"] to include rule notifications. |