Suspend or unsuspend a mailbox

POST


          /api/v1/email/account/actions/suspend

Try it

W Write

Scope write:email

This scope is inferred from the method and the endpoint's group — the OpenAPI document does not carry one per operation. The wire is authoritative; whoami reports what your token actually holds.

Description

POST suspends the mailbox (logins, delivery and sending stop; the mail stays); DELETE unsuspends it. The result reports the flag read back off the node. The main system account cannot be suspended here.

Body

Send as application/json.

Name	Type	Description
`address` required	string

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.

401 No token was presented, or the token is revoked, expired or unknown.

unauthorizedtoken_expiredtoken_revoked

403 The token lacks a required scope, or this account does not own the resource.

insufficient_scope

422 Validation error

validation_failed

429 The rate limit for this token is exhausted. See `Retry-After`.

rate_limited

500 Something went wrong on our side. The failure is logged against `requestId`.

internal_error

curl -X POST "https://mcp.inleed.com/api/v1/email/account/actions/suspend" \ -H "Authorization: Bearer inl_live_…" \ -H "Content-Type: application/json" \ -d '{"address":"[email protected]"}'

Description

Body

Responses

Commonly returned errors

Related endpoints