GET /api/v2/incremental/tickets
Returns the tickets that changed since the start time. For more information, see Exporting tickets in Using the Incremental Exports API.
This endpoint supports time-based incremental exports. For more information, see Time-based incremental exports in Using the Incremental Exports API. You can also return tickets using cursor-based pagination. See Incremental Ticket Export, Cursor Based.
The results include tickets that were updated by the system. See Excluding system-updated tickets in Using the Incremental Exports API.
The endpoint can return tickets with an updated_at
time that's earlier than the
start_time
time. The reason is that the API compares the start_time
with the ticket's
generated_timestamp
value, not its updated_at
value. The updated_at
value is
updated only if the update generates a ticket event.
The generated_timestamp
value is updated for all ticket updates, including system
updates. If a system update occurs after a ticket event, the unchanged
updated_at
time will become earlier relative to the updated generated_timestamp
time.
Allowed For
- Admins
Sideloading
See Tickets sideloads. For performance reasons,
last_audits
sideloads aren't supported.
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.