Revoke Retriever API Key

Revoke a retriever-scoped API key.

Effect:

• Key status is set to REVOKED
• Key can no longer be used for authentication
• Revocation is immediate (no grace period)
• Auth cache is invalidated immediately
• Cannot be undone (create a new key if needed)

Audit:

• Revocation is logged in the retriever’s audit trail
• Includes actor user ID and timestamp

DELETE /v1/retrievers/{retriever_id}/api-keys/{key_id}

Revoke Retriever API Key

cURL

curl --request DELETE \
  --url https://api.mixpeek.com/v1/retrievers/{retriever_id}/api-keys/{key_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Namespace: <api-key>'

200

{
  "message": "Successfully completed",
  "success": true
}

Authorizations

Authorization · string · header · required

Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.

X-Namespace · string · header · required

Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.

Path Parameters

retriever_id · string · required

key_id · string · required

Response

200

application/json

Successful Response

GenericSuccessResponse.

message · string · default: Successfully completed

success · boolean · default: true