Update Registration Policy
Change how new RBAC clients can join the endpoint. Effect is immediate — the next sign-up attempt is evaluated against the new policy. Existing clients are unaffected (suspending or removing them is a separate action via /status / DELETE .../rbac/clients/{client_uuid}).
Setting invite_only: true or allow_self_registration: false stops new self-registrations. Sessions for already-registered clients keep working until expiry. To force them out, use revoke-all per client (no bulk-revoke-everyone API right now).
Path parameters
uuid from /endpoints.Request body
All fields are optional; omitted booleans default to false. The whole policy is replaced on each save (it is not a partial merge of individual flags).
require_email_verification is on), whatever auto_approve says.uuid of the role to assign to newly self-registered clients. Must be one of this endpoint's roles.{"min_length": 8, "require_uppercase": true, "require_lowercase": true, "require_numbers": true, "require_special": false}.forward_user_email, custom_headers).Deprecated: default_role_id (integer) is still accepted until the sunset. Send default_role_uuid; sending both for different objects is a 400 id_uuid_mismatch.
Response (200 OK)
A confirmation object — not the updated policy. Re-read it via GET /v1/registration-policy if you need the saved values.
true on a successful save."Registration policy updated successfully".Errors
default_role_uuid (default_role_uuid must be a uuid), both forms naming different roles (id_uuid_mismatch), or an integer after the sunset (integer_id_unsupported).endpoints:update permission in the active account.default_role_uuid isn't one of this endpoint's roles (default_role_uuid not found; a legacy default_role_id of another endpoint is refused the same way).