renza

Errors

access_denied

Returned as permission_error with HTTP 403.

What happened

You're authenticated, but this credential doesn't have the right to do this — wrong org, insufficient role on the resource, or a scope the key lacks.

How to fix it

Confirm the active org and your role on the resource (grants control per-deck/folder access). If this is a service integration, check the key was created in the org you expect.

The envelope

{
  "error": {
    "type": "permission_error",
    "code": "access_denied",
    "message": "",
    "request_id": "req_8f2c4a1b",
    "doc_url": "https://docs.renza.io/errors/access_denied"
  }
}

See Errors for the full contract, and note the CLI maps this to a stable exit code — see Output & exit codes.