Revoke API key
Revoke one API Key owned by the current Registered User.
DELETE /api/v1/me/api-keys/{id}
OpenAPI operation revokeApiKey. Authenticate with a Clerk session JWT (Authorization: Bearer {jwt}) or the verbafy_guest_session cookie. {jwt} is a Clerk session token after you sign in on the website. Verbafy does not issue that token and does not show it in Settings. For scripts and agents, sign in, create an API key at Settings → API keys, and call Remote MCP with Authorization: Bearer sk-…. Credential setup: Auth.md. Machine-readable contract: OpenAPI.
Parameters
| Name | Location | Required | Type | Description |
|---|---|---|---|---|
id | path | Yes | string / uuid | API Key UUID owned by the current Registered User |
Request example
curl -X DELETE 'https://verbafy.io/api/v1/me/api-keys/{id}' \
-H 'Authorization: Bearer {jwt}'Responses
| Status | Description |
|---|---|
204 | Revoked |
401 | Missing or invalid Clerk Bearer token or guest session |
403 | Turnstile, ownership, or permission denied |
404 | Resource not found for the current account |
Remote MCP at /api/v1/mcp is a companion wrap of this REST contract.
List API keys
Hashed API Key metadata for the current Registered User. Guests receive 403. Secrets are never listed. GET /api/v1/me/api-keys on the Verbafy REST API.
Claim Guest data onto a Registered User
Browser transition that moves Guest Transcripts and Chats onto the Clerk Registered User. Requires both a Clerk Bearer token and the Guest session cookie