# Support

> Where to get help with dissolve.email, and the support tickets API for opening, reading and answering tickets from your own tools with an API key.

Source: https://docs.dissolve.email/support

## Getting help

| Where | For |
|---|---|
| The app's support page at app.dissolve.email | Opening a ticket and following its thread |
| support@dissolve.email | Anything, including a confidential OAuth client for a partner app |
| [status.dissolve.email](https://status.dissolve.email) | Whether something is down, incidents and maintenance |
| [Errors](/errors) | What an error code means and what to do about it |

When something fails, quote the `X-Request-Id` header of the answer (also in the body of a server error as `requestId`): it lets us find the request without seeing your data.

Every account can open tickets. On Business they are marked high priority and answered first.

## The support tickets API

The same tickets the app shows are open to an API key, so a test harness or an internal tool can report a problem with the inbox it happened on. These routes sit outside `/v1`: they take an `sk_live_` key (or the app's session), not an OAuth token.

### Open a ticket

`POST /api/support-tickets` (API key or signed-in session)

| Field | Required | Description |
|---|---|---|
| `subject` | yes | Up to 200 characters |
| `category` | yes | `billing`, `technical`, `account`, `feature_request` or `general` |
| `body` | yes | What happened, up to 10,000 characters |
| `inboxId` | no | One of your inboxes it is about |

Send JSON, or `multipart/form-data` with the same fields and up to 5 files whose field names start with `file` (each up to 10 MB: images, PDF, plain text or Word). At most 5 new tickets a day per account.

```bash cURL
curl -X POST https://api.dissolve.email/api/support-tickets \
  -H "Authorization: Bearer $DISSOLVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject": "Code never arrived", "category": "technical", "body": "The sign-up mail from example.com did not reach the inbox.", "inboxId": "V1StGXR8Z5jdHi6BmyT2k"}'
```

```bash cURL with a file
curl -X POST https://api.dissolve.email/api/support-tickets \
  -H "Authorization: Bearer $DISSOLVE_API_KEY" \
  -F subject="Code never arrived" -F category=technical \
  -F body="Screenshot attached." -F file1=@screenshot.png
```

```python Python
import os, requests

HEADERS = {"Authorization": f"Bearer {os.environ['DISSOLVE_API_KEY']}"}
ticket = requests.post(
    "https://api.dissolve.email/api/support-tickets",
    json={"subject": "Code never arrived", "category": "technical", "body": "The sign-up mail did not reach the inbox."},
    headers=HEADERS,
).json()
```

```json
{
  "id": "tkt2Nq8XcV5mLp1Rz7WbK",
  "userId": "usr7Np2QkX9mVc4Rt1ZbL",
  "inboxId": "V1StGXR8Z5jdHi6BmyT2k",
  "subject": "Code never arrived",
  "category": "technical",
  "priority": "normal",
  "status": "open",
  "assignedTo": null,
  "createdAt": "2026-11-19T10:10:00.000Z",
  "updatedAt": "2026-11-19T10:10:00.000Z",
  "resolvedAt": null,
  "attachments": []
}
```

### Follow a ticket

`GET /api/support-tickets` (API key or signed-in session)

Your tickets, the most recently changed first, and whether your plan has priority support.

`GET /api/support-tickets/{id}` (API key or signed-in session)

One ticket with its thread of messages, yours and ours.

| `status` | Means |
|---|---|
| `open` | Waiting for us |
| `in_progress` | Someone is on it |
| `waiting_customer` | We asked you something |
| `resolved` | We think it is fixed |
| `closed` | Done; it takes no more replies |

### Reply and close

`POST /api/support-tickets/{id}/messages` (API key or signed-in session)

Takes `body` (JSON or multipart) and files the same way as opening one. A reply to a ticket that is `waiting_customer` or `resolved` opens it again. At most 60 replies a minute.

`PATCH /api/support-tickets/{id}/close` (API key or signed-in session)

`GET /api/support-tickets/{id}/attachments/{attachmentId}` (API key or signed-in session)

A file from the thread, always sent as a download.
