Skip to main content

Add Support Ticket Note

POST 
/api/support/tickets/:ticket/notes

Adds a private note to the ticket, visible only inside your own organisation.

Required scope: support:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

It is the mirror of the internal notes SKU.io keeps on a ticket: yours are never shown to SKU.io support, and theirs are never shown to you. Use it to record what you chased, who you asked internally, or what to check next — the sort of thing that belongs on the ticket but is not a message to us.

Notes come back from GET /api/support/tickets/{ticket}/messages with kind: customer_note, alongside the public conversation, and are visible to every colleague who can see the ticket.

A note changes nothing else about the ticket: it does not reopen a resolved one, does not move the status, does not restart the response clock, does not notify anyone, and is not counted in public_messages_count.

Request body:

  • body (required, string, max 65000) — the plain-text form of the note
  • body_html (optional, string, max 200000) — the same note as formatted markup, sanitised to the same small tag set a reply accepts

Notes carry no attachments and no CC — they are never sent anywhere.

Authentication: Bearer token with the support:write scope, or an authenticated session, from a user who can view the ticket. A caller whose support seat is the viewer role is refused with 403. Requires the X-Tenant-Id header (or a tenant subdomain).

If this ticket was merged into another ticket, the request is refused with a 422 whose merged_into (id, number) names the live ticket — write the note there instead.

Request​

Responses​

Created

Response Headers
    Content-Type