POST · Support
Hold a support email for confirmation
Hold a support email for confirmation
/api/v1/support/requests
Description
Validates and returns {status:"confirmation_required", confirmationUrl, …} with the message preview. It emails no one — the human approves in the client area, and only then is the email sent from the account's own address. Poll get_pending_action for the outcome.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
subject
required
|
string |
The ticket subject line (max 191 chars), e.g. Email not delivering to Gmail.
|
message
required
|
string | The full message to support (max 10000 chars). Describe the problem, the affected domain/service, and what was already tried. |
attempt_key
|
string | Idempotency key for this intent. Keep it stable across retries so a timed-out retry cannot buy the same thing twice. Up to 128 characters. |
Responses
A 200 response returns the shape shown in the rail.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.