---
title: "Incremental Ticket Event Export"
method: GET
path: "/api/v2/incremental/ticket_events"
tags: ["Incremental Export"]
---

# Incremental Ticket Event Export

`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](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#exporting-ticket-events) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api)
- [Time-based incremental exports](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#time-based-incremental-exports) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-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:

```js
"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": "&lt;div class="zd-comment"&gt;&lt;p dir="auto"&gt;This is a comment&lt;/p&gt;",
    "public": true,
    "attachments": [],
    "audit_id": 91048994468,
    "created_at": "2009-06-25T10:15:18Z",
    "event_type": "Comment"
  },
  ...
],
...
```

## Response `200`

Success response

- ExportIncrementalTicketEventsResponse
  - `count` integer
  - `end_of_stream` boolean
  - `end_time` integer
  - `next_page` string, nullable
  - `ticket_events` TicketMetricEventBaseObject[]
    - `deleted` boolean — If true, the event has been deleted
    - `id` integer — Automatically assigned when the record is created
    - `instance_id` integer — The instance of the metric associated with the event. See [instance_id](#instance_id)
    - `metric` 'agent_work_time' | 'pausable_update_time' | 'periodic_update_time' | 'reply_time' | 'requester_wait_time' | 'resolution_time' | 'group_ownership_time' — The metric being tracked
    - `ticket_id` integer — Id of the associated ticket
    - `time` string, date-time — The time the event occurred
    - `type` 'activate' | 'pause' | 'fulfill' | 'apply_sla' | 'apply_group_sla' | 'breach' | 'update_status' | 'measure' — The type of the metric event. See [Ticket metric event types reference](/documentation/ticketing/reference-guides/ticket-metric-event-types-reference)

---

[API](https://skmtc.net/botbrains-io/apis/support-api.md) · [All operations](https://skmtc.net/botbrains-io/apis/support-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/botbrains-io/support-api/versions/d53eac07ba68/schema)
