Revoke the API key used for this request
Revokes the key this request authenticated with and answers 204 with no body. Takes no id, so it cannot revoke any other key. Called by imagestep logout.
- The key stops working at once on the instance that answered; another instance that has validated it recently may accept it for up to 30 seconds more. Stop using the key after this call rather than racing that window.
- Not repeatable: a second call cannot authenticate and answers 401 — after your own revoke, that means it worked.
- A signed-in session (Bearer) has no key behind it and gets 400 invalid_state; it revokes a key by id instead (DELETE /api/v1/api-keys/{keyId}, session only).
Request
- Base URL: https://api.imagestep.dev
- URL: https://api.imagestep.dev/api/v1/api-keys/self
- Auth: API key in header Authorization
Headers
Optional. A client-generated unique key (typically a UUID). Same key + the same request (method, path, query string and body) replays the first response verbatim with Idempotency-Replayed: true, without executing again. Same key + a different one returns 409 idempotency_key_reuse. A repeat that arrives while the first is still running returns 409 request_in_progress, which is retryable. Keys are retained 24 hours. At most 255 characters; a longer one is a 400 invalid_param with param: "Idempotency-Key".
Response
The calling key is revoked; from now on it answers 401
Changes
No recorded changes to this operation across all 1 revision of this API.