Skip to content
deedglassdocs

api_key_revoked

Step 4: the key passed the hash check, and someone in your org revoked it.

HTTP 401 · authentication_error · not retryable

What happened

Section titled “What happened”

Step 4: the key passed the hash check, and someone in your org revoked it. Every Deedglass instance refuses a revoked key within 2 seconds. Only someone holding the real secret ever sees this code, and it doesn’t count toward the failed-auth limiter. The response carries the WWW-Authenticate challenge with error="invalid_token".

What to do

Section titled “What to do”

Create a new key in Console › Agents and replace the old one wherever the agent reads it. A revoked key never works again.

Example

Section titled “Example”
HTTP 401 · api_key_revoked
{
  "error": {
    "type": "authentication_error",
    "code": "api_key_revoked",
    "message": "The API key has been revoked. Create a new key in Console › Agents.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/api_key_revoked"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) AuthenticationError with code === "api_key_revoked"
Python (deedglass) deedglass.AuthenticationError with .code == "api_key_revoked"
Section titled “Related”