Chimely
Api

Revoke an API key (soft; row kept for audit)

POST
/admin/api/environments/{env_id}/api-keys/{key_id}/revoke

Authorization

AdminSession
chimely_admin<token>

Server-side admin session cookie, set by POST /admin/api/login.

In: cookie

Path Parameters

env_id*string

Environment TypeID (env_…).

key_id*string

API key TypeID (key_…).

Response Body

application/json

application/json

curl -X POST "https://example.com/admin/api/environments/string/api-keys/string/revoke"
Empty
Empty
{
  "error": {
    "code": "invalid_request",
    "message": "string"
  }
}
{
  "error": {
    "code": "invalid_request",
    "message": "string"
  }
}

Replay one parked job (re-enters the normal claim path) POST

Moves the parked row back into `jobs` with a fresh attempt budget; the normal worker loop (SKIP LOCKED, per-environment fairness, delete-on-completion) runs it. Never executed inline.

Begin a subscriber-HMAC rotation (current → previous) POST

Generates a new current secret and moves the existing one into the previous slot. During the overlap BOTH secrets verify live `<Inbox />` sessions (auth checks current then previous), so rotation is zero-downtime. Complete the rotation to clear the previous slot once every customer backend has switched.