forbidden
HTTP status 403 · code: forbidden
The key is valid but may not do this: it lacks the scope the operation needs, its owner’s role no longer holds that permission, its owner is no longer an active member of the organisation or no longer holds API access, the organisation has turned API keys off (detail says so), or the organisation requires single sign-on for the owner and has not allowed keys for SSO-managed members.
What the answer carries
Section titled “What the answer carries”Every problem document carries type, title, status, code, detail and request_id. This code adds nothing to them.
What to do
Section titled “What to do”Create a key with the scope, ask an Admin to grant the owner’s role the permission, or ask an Admin to switch on Allow members to use API keys or Allow API keys for SSO-managed members on Organisation → Settings → Authentication. Retrying the same key cannot succeed until that changes.