---
title: "Update ticket / incident"
method: PATCH
path: "/v1/tickets/{id}"
tags: ["Tickets"]
---

# Update ticket / incident

`PATCH /v1/tickets/{id}`

**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

Update status, priority, assignee, title, or description. Broadcasts `incident.updated` (or `incident.resolved`) to all connected SSE clients.

## Path parameters

- `id` string, required

## Request body

- object
  - `title` string
  - `description` string
  - `status` 'open' | 'in_progress' | 'resolved' | 'closed'
  - `priority` 'low' | 'normal' | 'high' | 'urgent'
  - `assignee_id` integer, nullable
  - `lat` number, nullable
  - `lng` number, nullable
  - `location_name` string, nullable

## Response `200`

Default Response

- object

---

[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)