Roles not in plan

What the RbacDisabled error (402 Payment Required) means, the fields it carries, and the endpoints that return it.

The API answers 402 Payment Required with this problem. Its type is https://lingo.dev/docs/api/errors/rbac-disabled. See Errors and status codes for the shape every error shares.

Roles cannot be managed until organization <organizationId> holds the role-based access control entitlement. Every member currently carries the same access. Upgrade the plan to manage roles.

Fields #

Besides the standard type, status, title and detail members, the body carries these fields. The detail text is built from them, so a client can show its own text instead.

FieldType
organizationIdstring

Example #

json
{
  "detail": "Roles cannot be managed until organization <organizationId> holds the role-based access control entitlement. Every member currently carries the same access. Upgrade the plan to manage roles.",
  "organizationId": "<organizationId>",
  "type": "https://lingo.dev/docs/api/errors/rbac-disabled",
  "status": 402,
  "title": "Roles not in plan"
}

Returned by #

  • DELETE /v2/roles/{id}
  • GET /v2/organizations/{orgId}/audit-events
  • GET /v2/organizations/{orgId}/audit-events/{eventId}
  • PATCH /v2/invites/{id}
  • PATCH /v2/organizations/{orgId}/members/{userId}
  • PATCH /v2/roles/{id}
  • PATCH /v2/service-api-keys/{id}
  • POST /v2/organizations/{orgId}/invites
  • POST /v2/organizations/{orgId}/roles
  • POST /v2/organizations/{orgId}/service-api-keys
  • POST /v2/organizations/{orgId}/service-api-keys/scim
  • PUT /v2/service-api-keys/{id}/content-scope
  • PUT /v2/service-api-keys/{id}/engines