---
title: "Write to OpenEmail support"
description: "A message to the people who build OpenEmail, answered by email."
url: "https://openemail.uk/docs/api/support/send"
area: "API"
category: "Mailbox"
---

# Write to OpenEmail support

A message to the people who build OpenEmail, answered by email.

`POST /support`

## POST /support

A message to the people who build OpenEmail, answered by email.

## Example

Needs no scope. `topic` says what it is about in a few words and `message` is the message, up to 8,000 characters. The name and the reply address come from the account behind the call: the workspace owner for an API key, and the person who connected the app for an access token. Answers 201.

**curl**

```
curl -X POST "$OE/support" -H "$AUTH" -H "Content-Type: application/json" \
  -d '{ "topic": "Bug report", "message": "Scheduled sends to one address stay queued since this morning." }'
```

**Response**

```
{
  "object": "support_request",
  "id": "5d0c1f7e-2b8a-4c39-9e61-0f4a7b2d8c13",
  "replyTo": "ana@acme.com"
}
```

> One address can send 3 messages in 10 minutes. The next one is a 429 `support_rate_limited`, and nothing is recorded or sent.

> The workspace is named in the message, so support knows which one it is about. Sending the same request twice sends two messages.

## Reference

- [`POST /support`](https://openemail.uk/docs/api/reference/support#post-support): full reference