Revoke an API key (admin)
/api/keys/{id}A soft delete: revoked_at is stamped and the row stays, so the record of what existed, who issued it and what it could reach survives revoking it. That matters precisely when a key is being revoked in a hurry because it leaked, which is the worst possible moment to discard the evidence.
Revocation is immediate, with no cache to wait out; the gate reads revoked_at on every request.
Authorization
sessionCookie The dashboard's Supabase Auth session cookie, set at sign-in. Large sessions are split across
numbered chunks (…auth-token.0, .1), so treat this as a cookie family rather than one name.
Every request re-validates it against the Auth server (getUser()), never by decoding the cookie
locally: a JWT nothing has checked is not a credential. Tenancy is then read from the verified
app_metadata.company_id claim and enforced by row-level security; it is never read from request
input, on any route, ever.
role (admin / staff) is deliberately not in RLS. It gates specific actions in route code,
the operations marked admin below, so hiding a button in the UI is cosmetic only, and a route's
own check is the enforcement.
In: cookie
Path Parameters
The key id; the non-secret 16-hex segment of the token, not the token itself.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/api/keys/string"{ "ok": true}