Support tickets API

All endpoints under /api/support/tickets require a bearer token. Reading needs support:read, creating needs support:create, replying or closing needs support:update.

Prefer email? Writing to support@microapps.io opens a ticket too.

List your tickets

GET /api/support/tickets?page=1&limit=20&search=pod

Paginated. Returns the standard { data, total, page, limit, totalPages } envelope.

Get a ticket

GET /api/support/tickets/:id

Returns the ticket with its full messages thread (yours and ours), in order.

Create a ticket

POST /api/support/tickets

{
  "subject": "Cannot start my pod",
  "category": "technical",
  "message": "I clicked start and it flips straight back to stopped."
}

category is one of:

Category	Use it for
general	Anything that does not fit below
billing	Credit, invoices, payments
technical	Something is broken or behaving oddly
account	Login, profile, team, access
feature	"It would be great if..."

Reply to a ticket

POST /api/support/tickets/:id/replies

{ "message": "Here is the log output you asked for..." }

Replying to a ticket that is waiting on you flips it back to open. Closed or resolved tickets reject replies with a 400.

Close a ticket

PATCH /api/support/tickets/:id/close

Marks the ticket closed. Closed and resolved tickets don't take replies - open a new ticket if there's more to say.

Ticket status

A ticket moves through these as we work it, and you will see the current one on the ticket:

Status	Meaning
open	We have it, not started yet
inProgress	Someone is on it
waiting	We are waiting on you, usually for a reply
resolved	We think it is sorted
closed	Done, or you closed it

curl example

curl -X POST https://cloud-api.microapps.io/api/support/tickets \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"subject":"Cannot start my pod","category":"technical","message":"..."}'