GET /api/v2/incremental/ticket_events
Returns a stream of changes that occurred on tickets, excluding events occuring within one minute of the request. Each event is tied to an update on a ticket and contains all the fields that were updated in that change. For more information, see:
- Exporting ticket events in Using the Incremental Exports API
- Time-based incremental exports in Using the Incremental Exports API
You can include comments in the event stream by using the comment_events
sideload. See Sideloading below. If you don't specify the sideload, any comment
present in the ticket update is described only by Boolean comment_present
and comment_public
object properties in the event's child_events
array.
The comment itself is not included.
Allowed For
- Admins
Sideloading
The endpoint supports the comment_events
sideload. Any comment present in the ticket
update is listed as an object in the event's child_events
array. Example:
"child_events": [
{
"id": 91048994488,
"via": {
"channel": "api",
"source": {"from":{},"to":{},"rel":null}},
"via_reference_id":null,
"type": "Comment",
"author_id": 5031726587,
"body": "This is a comment",
"html_body": "<div class="zd-comment"><p dir="auto">This is a comment</p>",
"public": true,
"attachments": [],
"audit_id": 91048994468,
"created_at": "2009-06-25T10:15:18Z",
"event_type": "Comment"
},
...
],
...
Servers
- https://{subdomain}.{domain}.com
Query parameters
Name | Type | Required | Description |
---|---|---|---|
start_time |
Integer | Yes |
The time to start the incremental export from. Must be at least one minute in the past. Data isn't provided for the most recent minute |
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.