Partially update a tenant

Applies a JSON Merge Patch to the tenant's name. Only provided
fields are updated.

Note: deploymentType is NOT patchable. It is a
platform-managed attribute auto-populated from
deployment_info. Any request containing
deploymentType is rejected with HTTP 400.

status is NOT patchable here, and never was legitimately. The tenant
lifecycle is a state machine with exactly one entry point per transition, on the PLATFORM
plane: PATCH /api/v3/admin/platform/tenants/{tenantId}/activate
(PROVISIONING → ACTIVE), .../suspend
(ACTIVE → SUSPENDED) and .../reactivate
(SUSPENDED → ACTIVE). Each asserts its exact source state and answers
HTTP 422 otherwise, and each is gated on its own
admin.tenant.lifecycle.* scope. The terminal CLOSED state is

reached only by DELETE /api/v3/admin/platform/tenants/{tenantId}, which
pairs it with the soft-delete. A request carrying status is rejected with
HTTP 400 (Jackson FAIL_ON_UNKNOWN_PROPERTIES) rather than silently ignored.

Access Control: Tenant Administrators can only update their own tenant.
Platform Administrators can update any tenant (ROOT_TENANT requires ROLE_PLATFORM_ROOT).

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

Tenant UUID

Body Params

JSON object carrying:
name: new tenant name

No other field is accepted. In particular there is no status field —
lifecycle transitions live on the platform-plane endpoints named in the operation
description.

Payload used to update a tenant attributes

string
length between 1 and 255
^\S+( \S+)*$

New tenant name

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