> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usertick.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Usertick runs surveys on websites, by link, by QR code and by email, and collects every response in one inbox with reports, dashboards and workflows. The REST API lives at https://app.usertick.com/api/public/v1 and uses Bearer API keys or OAuth access tokens; the JavaScript SDK is the @usertick/snippet package on npm.

# Support tickets

> Open Usertick support tickets for the person an app or an AI assistant acts as, list that person's tickets and read and answer support's replies through the REST API.

The support ticket endpoints open, list and answer the same tickets as **Help & support** in Usertick. A ticket belongs to the person who opens it, so these endpoints work only for an [app](https://docs.usertick.com/developers/api/oauth.md) or an [AI assistant](https://docs.usertick.com/developers/mcp.md) that a member connected, and they reach only the tickets that member opened in the organization.

| Endpoint | Scopes | Does |
| - | - | - |
| [`GET /support/tickets`](https://docs.usertick.com/developers/api/reference/list-support-tickets) | `support:read` | Lists the person's tickets |
| [`GET /support/tickets/{ticketId}`](https://docs.usertick.com/developers/api/reference/get-support-ticket) | `support:read` | Returns one ticket with its messages |
| [`POST /support/tickets`](https://docs.usertick.com/developers/api/reference/create-support-ticket) | `support:write`, `support:read` | Opens a ticket as the person |
| [`POST /support/tickets/{ticketId}/messages`](https://docs.usertick.com/developers/api/reference/reply-support-ticket) | `support:write`, `support:read` | Adds the person's reply |

An API key acts as the organization rather than a person, so it can't hold these scopes, and a request with an API key returns `403` with `PUB-017-002`.

## Open a ticket

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl https://app.usertick.com/api/public/v1/support/tickets \
  -H "Authorization: Bearer $USERTICK_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: widget-checkout-2026-11-13" \
  -d '{
    "kind": "setup",
    "subject": "The widget doesn'\''t show on the checkout page",
    "body": "I added the install code to my site, but the survey doesn'\''t show on the checkout page."
  }'
```

`kind` takes the categories of the ticket window: `contact` (the default), `setup`, `targeting`, `integrations`, `billing` or `bug`. `subject` holds up to 200 characters and `body` up to 10,000. Usertick attaches the organization's plan, as it does for a ticket opened in the dashboard.

The call returns `201` with the ticket, its first message and its address in `Location`. Support answers in the order the plan gives, and its replies reach the person under **Help & support** and by email. If you send the request again with the same `Idempotency-Key` within 24 hours, it returns the same ticket.

Support tickets are included in the paid plans, so on Free, opening a ticket or replying returns `403` with `SUP-004-001`. Each ticket appears in the activity log under the person's name, followed by "via" and the app's or the assistant's name.

## List and read tickets

`GET /support/tickets` lists the person's tickets, the latest message first. `status` narrows the list to `open` (waiting or answered), `waiting`, `answered` or `closed`, and `search` finds a word in the subject or the first message, or a ticket's number such as `42` or `#42`.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "id": "c1d2e3f4-a5b6-4c7d-8e9f-0a1b2c3d4e5f",
  "number": 1042,
  "subject": "The widget doesn't show on the checkout page",
  "kind": "setup",
  "status": "answered",
  "messageCount": 2,
  "createdAt": "2026-11-13T09:30:00.000Z",
  "lastMessageAt": "2026-11-13T11:05:00.000Z",
  "closedAt": null,
  "url": "https://app.usertick.com/help/tickets/c1d2e3f4-a5b6-4c7d-8e9f-0a1b2c3d4e5f?org=3c9e4e1a-5b7d-4f20-9a61-0c2d8e4f6a10"
}
```

* `status` is `waiting` while support hasn't answered the last message, `answered` when support's message is the last, and `closed` once the ticket is closed.
* `url` opens the ticket under **Help & support**, where the person can read the replies and download the files support sent.

`GET /support/tickets/{ticketId}` returns the ticket with a page of its messages, newest first, and `limit` and `cursor` page through the older ones. Each message says whether it came from the `customer` or from `support`, and a message of kind `event` notes something such as support taking the ticket. A ticket another member opened returns `404` with `PUB-017-001`, the same as an unknown ID. Reading a ticket through the API leaves its new reply mark in Usertick as it was.

## Reply on a ticket

`POST /support/tickets/{ticketId}/messages` takes `body`, up to 10,000 characters, and returns `201` with the message. A reply to a closed ticket reopens it, as it does in Usertick.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.