When using time-based incremental exports, subsequent pages and exports use the start_time parameter. To prevent race conditions, the ticket and ticket event export endpoints will not return data for the most recent minute. The time must be more than one minute in the past to avoid missing data. The start_time of the initial export is arbitrary. GET /api/v2/incremental/tickets/cursor.json?start_time=1532034771 All endpoints require a start_time parameter for the initial export.

Specifies a time expressed as a Unix epoch time. Whether or not you'd like to exclude deleted tickets from the response. If the parameter is not specified, the default number is 1,000. Number of results to return per page, up to a maximum of 1,000. The format depends on the exported resource and pagination type, but all have the following additional common attribute:Ī start time expressed as a Unix epoch time. The exported items are represented as JSON objects. We recommend using the Retry-After header value as described in Catching errors caused by rate limiting. The rate limiting mechanism behaves identically to the one described in Rate limits. You can make up to 10 requests per minute to these endpoints. To learn more, see the following topics in Using the Incremental Export API: Response: 'Here are the tickets that changed since 5pm up until, and including, 7pm.'.Request at 7pm: 'Give me the tickets that changed since 5pm.'.

Response: 'Here are the tickets that changed since noon up until, and including, 5pm.'.Request at 5pm: 'Give me all the tickets that changed since noon today.'.Use the incremental export API to get items that changed or were created in Zendesk Support since the last request.

Ticket json query string