curl -X DELETE "https://api.nevia.cloud/v1/workspaces/01d4cnjjq40hnnh0nwmkg35nv2h/access/01d4cnjmn4fbb1r5btxb5mypv62/key" \
-H "Authorization: Bearer $TOKEN"{
"key": {
"id": "01d4cnjq8r0tvwxyb3c4d5f6g7h",
"principal": "01d4cnjmn4fbb1r5btxb5mypv62",
"byok": true,
"created_by": "01d4cnjmn4fbb1r5btxb5mypv62",
"expires_at": "2026-09-10T12:34:56Z",
"last_used_at": "2026-09-10T12:34:56Z",
"created_at": "2026-09-10T12:34:56Z",
"revoked_at": "2026-09-10T12:34:56Z"
},
"operations": [
"01d4cnjm89yk0r3xtv80dy0x7by"
]
}Authorization
bearerAuth Send the token in the Authorization: Bearer <token> header. See Authenticate.
In: header
Path Parameters
Workspace id: 27 lowercase letters and digits.
^[A-Za-z0-9_-]{1,64}$Principal id: 27 lowercase letters and digits.
^[A-Za-z0-9_-]{1,64}$Header Parameters
Optional retry key, kept 24 hours
1 <= length <= 255Behavior
The key is addressed through the principal, so no key id is needed. Every access token the principal holds at this moment is refused on its next request with 401 token_revoked. An expired key is revoked the same way, since the tokens it minted may still be in use. The principal keeps its access, and its key_state reads revoked until the next rotation. Revoking an already revoked key returns it again.
Response
application/jsonThe revoked key, as it stands after revocation.