---
title: "List tickets / incidents"
method: GET
path: "/v1/tickets"
tags: ["Tickets"]
---

# List tickets / incidents

`GET /v1/tickets`

**Tickets and incidents are the same object.** Every record in this table is accessible via both `/v1/tickets` and the real-time `/v1/incidents` layer — same NocoDB row, same ID, same fields. No data is duplicated.

- Use `/v1/tickets` for helpdesk, ITSM, or async workflows
- Use `/v1/incidents` + SSE for real-time dispatch, ops war rooms, or alert routing
- The `source` field (`api`, `email`, `webhook`, `alert`) and `priority` together imply context — neither endpoint enforces a use case on the caller

Returns records for the authenticated user. Filter by `status` or `priority`. Paginated.

## Query parameters

- `status` 'open' | 'in_progress' | 'resolved' | 'closed'
- `priority` 'low' | 'normal' | 'high' | 'urgent'
- `limit` integer
- `page` integer

## Response `200`

Default Response

- object
  - `tickets` object[]
    - `sla_due_at` string, nullable
    - `sla_breached` boolean
    - `sla_status` 'ok' | 'warning' | 'breached'
    - `customer_token` string — Magic token for public customer status page
  - `total` integer

---

[API](https://skmtc.net/schedkit/apis/schedkit-api.md) · [All operations](https://skmtc.net/schedkit/apis/schedkit-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/schedkit/schedkit-api/revisions/ff810218c3f4/schema)