API Documentation

Support Tickets API

Programmatic access to file, list, and manage support tickets. Tickets created here flow into the same internal CRM used by the dashboard at /dashboard/support.

POST/api/support-tickets

Create a new support ticket. Authenticated requests use the session user's identity automatically. For anonymous callers, email is required.

Request body

{
  "subject": "Cannot connect WhatsApp channel",
  "body": "Verification webhook returns 403 every time...",
  "email": "user@example.com",
  "name": "Jane Doe",
  "category": "bug",
  "priority": "high"
}

Response (201)

{ "success": true, "ticketId": "clx123abc", "message": "Support ticket created. Check your email for confirmation." }

Both the submitter and the support inbox receive an email.

GET/api/support-tickets

List tickets you submitted. Admins can pass ?scope=all to see every ticket and combine with ?status=, ?priority=, ?assignedToMe=true, ?q= (subject / email search), ?cursor=, ?limit=.

Response (200)

{
  "success": true,
  "data": [ { "id": "clx123abc", "subject": "...", "status": "open", "priority": "normal" } ],
  "nextCursor": null
}

GET/api/support-tickets/{ticketId}

Fetch a single ticket including its message thread. Internal notes are only included when the caller is an admin.

PATCH/api/support-tickets/{ticketId}

Admin-only. Update status, priority, category, or assignedToId. Status changes trigger an email to the submitter.

Statuses

open — submitted, awaiting first response
in_progress — being investigated
awaiting_user — awaiting reply from submitter
resolved — fix delivered, awaiting confirmation
closed — finalized; replies disabled

POST/api/support-tickets/{ticketId}/messages

Add a reply to the thread. Owners and admins can post replies. Admins can pass isInternal: true to add a note that is not emailed to the user.

Request body

{ "body": "Thanks — could you share a screenshot?", "isInternal": false }

Need help?

Use the support guide to learn how status changes are emailed and how to track a ticket end-to-end.

API Documentation

Support Tickets API

Programmatic access to file, list, and manage support tickets. Tickets created here flow into the same internal CRM used by the dashboard at /dashboard/support.

POST/api/support-tickets

Create a new support ticket. Authenticated requests use the session user's identity automatically. For anonymous callers, email is required.

Request body

{
  "subject": "Cannot connect WhatsApp channel",
  "body": "Verification webhook returns 403 every time...",
  "email": "user@example.com",
  "name": "Jane Doe",
  "category": "bug",
  "priority": "high"
}

Response (201)

{ "success": true, "ticketId": "clx123abc", "message": "Support ticket created. Check your email for confirmation." }

Both the submitter and the support inbox receive an email.

GET/api/support-tickets

List tickets you submitted. Admins can pass ?scope=all to see every ticket and combine with ?status=, ?priority=, ?assignedToMe=true, ?q= (subject / email search), ?cursor=, ?limit=.

Response (200)

{
  "success": true,
  "data": [ { "id": "clx123abc", "subject": "...", "status": "open", "priority": "normal" } ],
  "nextCursor": null
}

GET/api/support-tickets/{ticketId}

Fetch a single ticket including its message thread. Internal notes are only included when the caller is an admin.

PATCH/api/support-tickets/{ticketId}

Admin-only. Update status, priority, category, or assignedToId. Status changes trigger an email to the submitter.

Statuses

open — submitted, awaiting first response
in_progress — being investigated
awaiting_user — awaiting reply from submitter
resolved — fix delivered, awaiting confirmation
closed — finalized; replies disabled

POST/api/support-tickets/{ticketId}/messages

Add a reply to the thread. Owners and admins can post replies. Admins can pass isInternal: true to add a note that is not emailed to the user.

Request body

{ "body": "Thanks — could you share a screenshot?", "isInternal": false }

Need help?

Use the support guide to learn how status changes are emailed and how to track a ticket end-to-end.