reseller

POST /v1/reseller/support/tickets/{ticketId}/close

Close a client ticket.

All reseller endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

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

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

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/reseller/support/tickets/{ticketId}/close \
  -H "Authorization: Bearer zdk_live_…"

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

Closes the ticket. Closing a closed ticket changes nothing. Requires reseller.manage.

Parameters

NameTypeRequiredWhat it is
ticketId (path)UuidYesThe client ticket's id.
org_id (query)UuidNoWhich of your organizations this applies to.

Response

NameTypeRequiredWhat it is
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.
client_org_idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
client_namestringYesYour client's organization name.
created_atstringYes—
updated_atstringYes—
escalated_ticket_idobjectYesThe ticket in your own organization this was escalated to us as, if any.
messagesResellerSupportMessage[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429