Insufficient Permission

insufficient-permission · 403

The 403 the API's OpenAPI document advertises, with requiredPermission naming the permission the caller lacks.

At runtime a refused permission answers forbidden-access instead, so handle both.

Besides the members every error carries, this type adds requiredPermission.

Common causes

  • The account doesn't hold the permission the operation needs, such as cloud:projects:delete.

How to fix the call

  • Read requiredPermission and tell the user exactly which permission is missing.
  • Don't retry, and don't attempt the same change through a different endpoint.

Example response

json
{
  "type": "insufficient-permission",
  "title": "Insufficient Permission",
  "status": 403,
  "detail": "Your account is not permitted to perform this action (missing: cloud:projects:delete)",
  "requiredPermission": "cloud:projects:delete",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "method": "DELETE",
  "instance": "DELETE /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "docs": "https://ghaym.me/docs/errors/insufficient-permission"
}