# POST /api/v1/support/requests

> Hold a support email for confirmation

- Group: support
- Tier: W
- Required scope: write:support
- Docs: https://api.inleed.com/reference/support/create-support-request

## 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

- `subject` — string (required). The ticket subject line (max 191 chars), e.g. Email not delivering to Gmail.
- `message` — string (required). 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.

## Request

```bash
curl -X POST "https://mcp.inleed.com/api/v1/support/requests" \
  -H "Authorization: Bearer inl_live_…" \
  -H "Content-Type: application/json" \
  -d '{"subject":"example.se","message":"Resolved via the owning account.","attempt_key":"example.se"}'
```

## Response · 200

```json
{
  "status": "active",
  "pendingActionId": "example.se",
  "confirmationUrl": "https://mcp.inleed.com/…",
  "expiresAt": "2026-08-30T09:12:44.000Z",
  "preview": []
}
```

## Errors

- **401** No token was presented, or the token is revoked, expired or unknown. — codes: unauthorized, token_expired, token_revoked
- **403** The token lacks a required scope, or this account does not own the resource. — codes: insufficient_scope
- **422** Validation error — codes: validation_failed
- **429** The rate limit for this token is exhausted. See `Retry-After`. — codes: rate_limited
- **500** Something went wrong on our side. The failure is logged against `requestId`. — codes: internal_error