Sign in

v1

latestOpenAPI 3.0.32026-07-131670112.4 KB
Tickets

Update ticket / incident

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.

patch/v1/tickets/{id}

Path parameters

idstring required

Request body

titlestring
descriptionstring
status'open' | 'in_progress' | 'resolved' | 'closed'
priority'low' | 'normal' | 'high' | 'urgent'
assignee_idinteger nullable
latnumber nullable
lngnumber nullable
location_namestring nullable

Response

Default Response

object required

Example response

{
  "Id": 42,
  "title": "Water main pressure drop",
  "description": "Pressure dropped below threshold at Site Alpha.",
  "status": "in_progress",
  "priority": "high",
  "source": "alert",
  "source_ref": "sensor-ops-991",
  "user_id": 7,
  "sla_due_at": "2026-03-15T19:00:00Z",
  "sla_breached": false,
  "sla_status": "warning",
  "customer_token": "cus_tok_abc123xyz",
  "customer_status_url": "https://schedkit.net/incidents/status/cus_tok_abc123xyz",
  "lat": 35.4676,
  "lng": -97.5164,
  "location_name": "Site Alpha North Gate",
  "assignee_id": 12
}