support

POST /v1/tickets

Open a support ticket.

All support endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the tickets.reply permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/tickets \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "subject": <string>, "body": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Opens a ticket in open with the supplied body as its first message, and publishes ticket.created (which sends the customer a localized acknowledgement via the notification consumer). channel is server-decided — it is not accepted from the client. A supplied site_id or invoice_id must belong to the same org or the request is a 404. Requires tickets.reply.

Request body

NameTypeRequiredWhat it is
subjectstringYes—
bodystringYesThe customer's description — becomes the first message in the thread.
priorityTicketPriorityNoHow urgent the ticket is. The customer may propose one; staff decide.
site_idstringNoThe site this is about. Must belong to the same org or the request is a 404.
invoice_idstringNoThe invoice this is about. Must belong to the same org or the request is a 404.
org_idstringNoThe organization to open it in. Required only when the caller holds tickets.reply in more than one org.
on_behalf_of_org_idstringNoThe client org this is about — a reseller escalating to Zinn® on their client's behalf. Must be a descendant of the ticket's org or the request is a 404; your client never…
deflection_idstringNoThe AI answer (POST /v1/tickets/deflect with ask_ai) the customer saw before choosing "Still need help" (s1014 L39) — counted as answered-then-ticketed.
grant_accessbooleanNo"Give support access to this site" (s1014 L39): the customer's consent for staff to sign in to site_id while this ticket is open, for 7 days at most. Ignored without site_id.…

Response

NameTypeRequiredWhat it is
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
org_idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
subjectstringYes—
statusTicketStatusYesWhere a ticket sits in its lifecycle. open = waiting on us; pending = waiting on the customer; solved = we believe it is resolved and a customer reply reopens it; closed =…
priorityTicketPriorityYesHow urgent the ticket is. The customer may propose one; staff decide.
channelstringYesHow the ticket reached us — dashboard, api or staff. Server-decided; an open string so a future channel is additive on both sides.
site_idobjectNo—
invoice_idobjectNo—
on_behalf_of_org_idobjectNoThe client org a reseller opened this ticket about. Null on every ordinary ticket. ⛔ Validated as a descendant of the ticket's own org and 404d otherwise, so it can never…
assignee_nameobjectYesThe owning agent's display name (first name), or null while unassigned. The customer sees a name so they know a person owns their ticket; the agent's id and email are…
first_response_atobjectNo—
resolved_atobjectNo—
closed_atobjectNo—
last_message_atobjectNo—
reopened_countintegerYes—
message_countintegerYesCustomer-visible messages in the thread — internal notes are not counted.
created_atstringYes—
updated_atstringYes—
messagesTicketMessage[]YesThe customer-visible thread in chronological order.
accessTicketAccessGrant[]YesSite access the customer gave support on this ticket (s1014 L39).

Errors this endpoint can return

401 · 403 · 404 · 422 · 429