Revoke a key

Revokes the key for good. The answer is {"deleted": true}, also when another request revoked it first.

DEL/api/v1/keys/{hash}

Your key

Request

curl -X DELETE https://api.llm.buzz/api/v1/keys/{hash} \
  -H "Authorization: Bearer $LLM_BUZZ_MANAGEMENT_KEY"

Response

{
  "deleted": true
}

{
  "error": {
    "code": 401,
    "message": "Missing Authentication header",
    "metadata": {
      "error_type": "authentication",
      "gateway_code": "missing_authentication"
    }
  }
}

{
  "error": {
    "code": 403,
    "message": "Only management keys can perform this operation; use a management key, created on the console Keys page",
    "metadata": {
      "error_type": "permission_denied",
      "gateway_code": "management_key_required"
    }
  }
}

{
  "error": {
    "code": 404,
    "message": "No API key has this hash. GET /api/v1/keys lists the keys you manage.",
    "metadata": {
      "error_type": "not_found",
      "gateway_code": "key_not_found",
      "param": "hash"
    }
  }
}

Authorization

A management key, created on the console's Keys page, as Authorization: Bearer KEY. The samples read it from $LLM_BUZZ_MANAGEMENT_KEY; an inference key gets 403 management_key_required.

Keys and limits

Parameters

hashstringpathrequired
The key's hash, as GET /api/v1/keys lists it.

Response 200

The key is revoked.

Errors

401
No Authorization header (missing_authentication), or the key is unknown, expired, revoked or disabled (invalid_key).
403
An inference key called a route that takes a management key. Create one on the console's Keys page.
404
The hash names none of your inference keys.

Every error code