Access Forbidden

forbidden · 403

The fallback type for a 403 that has no named type, and no route in the API sends it today.

A refused permission or a seat role too low for the call answers forbidden-access, which names what was missing.

This type adds no members to the ones every error carries.

Common causes

  • A 403 raised without a type of its own reached the error handler.

How to fix the call

  • Don't retry, and don't try another endpoint hoping it is less restricted.
  • Show detail to the user and let them decide: a permission change is theirs to make.

Example response

json
{
  "type": "forbidden",
  "title": "Access Forbidden",
  "status": 403,
  "detail": "Forbidden resource",
  "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/forbidden"
}