Suspend tenant (ACTIVE -> SUSPENDED)

Temporarily disables crypto and login capabilities for the tenant. Admin read access
is preserved. Publishes a signed status envelope to Redis and emits an admin audit event.

A reason is mandatory. Suspension is the transition that removes a

paying customer's capability and the one a customer disputes, so the operator's
justification is recorded verbatim on the admin audit event and signed with it. The
sibling verbs activate and reactivate take no body: both restore
capability and generate no grievance to answer.

Omitting the reason, or sending it blank or whitespace-only, is refused with 400 application/problem+json and the tenant's status is unchanged. A

request carrying no Content-Type, or a non-JSON one, is refused with
415 before the body is read at all.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

Tenant UUID

Body Params

Carries the single mandatory field reason: the operator's free-text justification, 1 to 1000 UTF-8 BYTES (not characters: a Cyrillic or CJK justification costs 2-3 bytes per character), neither blank nor whitespace-only. It is written verbatim to the admin audit trail and is not interpreted by the server.

Request to suspend a tenant, carrying the operator's mandatory justification

string
required
length between 1 and 1000

Human-readable justification for the suspension (mandatory for the audit trail). Recorded verbatim on the admin audit event and signed with it.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json