GET /api/v2/triggers/{trigger_id}/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:

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.

Servers

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

Path parameters

How to start integrating

1. Add HTTP Task to your workflow definition.
2. 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.
3. Click Test request to test run your request to the API and see the API's response.