Support Tickets
The support ticket API mirrors the in-console Help → Support flow. Useful for bulk-automation (e.g. post-mortem triggers) and for integrations that want to raise tickets on behalf of users.
Endpoints
Section titled “Endpoints”| Method | Path | Description |
|---|---|---|
POST | /api/v1/support/tickets | Open a ticket. |
GET | /api/v1/support/tickets | List your tickets. |
GET | /api/v1/support/tickets/{id} | Read one. |
PATCH | /api/v1/support/tickets/{id} | Update (reopen, change subject). |
POST | /api/v1/support/tickets/{id}/messages | Append a message. |
POST | /api/v1/support/tickets/{id}/feedback | Submit CSAT after resolution. |
Authentication is session-only (logged-in user). API keys are not honoured on the support surface; tickets are inherently user-attributed.
Open a ticket
Section titled “Open a ticket”{ "subject": "Webhook deliveries to Opsgenie are intermittent", "priority": "normal", "initial_message": "Since ~17:00 UTC we're seeing 502s from the Opsgenie channel. Included alert IDs in the attached sheet.", "attachment_ids": []}priority | Meaning |
|---|---|
low | General question, no immediate impact. |
normal | Default; SLA per plan. |
high | Customer-facing impact. |
urgent | Production outage. Pro/Enterprise only. |
Append a message
Section titled “Append a message”POST /api/v1/support/tickets/{id}/messages{ "body": "Tried rotating the webhook secret; problem persists." }After a ticket moves to resolved, you can submit a satisfaction rating:
POST /api/v1/support/tickets/{id}/feedback{ "rating": 5, "comment": "Fast fix, thanks." }Ratings are 1-5. Optional comment is shown to the assigned staff member.