workspace_disabled

err:unkey:authorization:workspace_disabled

Your workspace is disabled, so every request made with its root keys fails, whatever the state of the key. You get HTTP 403. A dashboard session for a disabled workspace gets the same error with Your organization does not have an active workspace.

Example response

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The provided root key is invalid. The workspace is disabled.",
    "status": 403,
    "title": "Workspace is disabled",
    "type": "/errors/unkey/authorization/workspace_disabled"
  }
}

How to fix

You can’t turn a workspace back on yourself. Contact support with the requestId and your workspace ID, and ask why it was disabled. Until it’s back on, nothing works for the workspace, including key verification.

err:unkey:authorization:key_disabled: only the key is disabled.
err:unkey:data:workspace_not_found: the key points at a workspace that no longer exists.

Last modified on October 6, 2026

⌘I

Get started

Workspace

Audit logs

Billing

Root keys

API

CLI

AI coding

Security

Errors

How to fix

​How to fix

​Related errors

How to fix

Related errors