Triggers
List Ticket Trigger Revisions
List the revisions associated with a ticket trigger. Ticket trigger revision history is only available on Enterprise plans.
Allowed For
- Agents
Sideloads
The following sideloads are supported:
| Name | Will sideload |
|---|---|
| users | The user that authored each revision |
Pagination
This endpoint uses cursor-based pagination. The records are ordered in descending order by the created_at timestamp, then by id on duplicate created_at values.
The cursor parameter is a non-human-readable argument you can use to move forward or backward in time.
Each JSON response will contain the following attributes to help you get more results:
- after_url requests more recent results
- before_url requests older results
- after_cursor is the cursor to build the request yourself
- before_cursor is the cursor to build the request yourself
The properties are null if no more records are available.
You can request a maximum of 1000 records using the limit parameter. If no limit parameter is supplied, it will default to 1,000.
get/api/v2/triggers/{trigger_id}/revisions
Response
Success response
Example response
{
"trigger_revisions": [
{
"diff": {
"actions": [
{
"field": [
{
"change": "+",
"content": "solved"
}
],
"value": [
{
"change": "-",
"content": "open"
}
]
}
],
"active": [
{
"change": "+",
"content": "solved"
}
],
"conditions": {
"field": [
{
"change": "=",
"content": "status"
}
],
"operator": [
{
"change": "=",
"content": "less_than"
}
],
"value": [
{
"change": "+",
"content": "solved"
}
]
},
"description": [
{
"change": "+",
"content": "solved"
}
],
"title": [
{
"change": "+",
"content": "solved"
}
]
},
"snapshot": {
"actions": [],
"active": true,
"conditions": {},
"description": "Notifies requester that a comment was updated",
"title": "Notify requester of comment update"
}
}
]
}