Get Clerk API key
Retrieve API key metadata by id from a connected Clerk application.
← All Clerk endpoints · Capability overview
/v1/clerk/api-keys/{api_key_id}https://api.vee3.io/v1/clerk/api-keys/{api_key_id}
Retrieve API key metadata by id from a connected Clerk application.
Authorization
Send your API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY
MCP
The same capability is available as an MCP tool on Vee3 hosted MCP.
Tool name
clerk.get_api_keyParameters2 fields
clerk_instance_idstringOptionalClerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
api_key_idstringRequiredClerk API key id (ak_...) to retrieve, update, delete, or revoke.
Response17 fields
api_keyobject16 fieldsClerk API key metadata from the Backend API.
api_keyobjectidstringClerk API key id (ak_...).
namestringHuman-readable API key name.
subjectstringSubject the API key is scoped to (user_... or org_...).
key_typestringAPI key type (typically "api_key").
descriptionstringOptional description for the API key.
claimsobject1 fieldCustom claims embedded in tokens minted from this API key.
claimsobjectclaim_keystringA key in the custom claims object.
scopesarrayitems1 fieldPermission scopes granted to this API key.
scopesarrayitemsitemstringA single scope string.
created_bystringUser id that created the API key, when set.
created_atintegerUnix timestamp in milliseconds when the API key was created.
updated_atintegerUnix timestamp in milliseconds when the API key was last updated.
expirationintegerUnix timestamp in milliseconds when the API key expires, if set.
revokedbooleanWhether the API key has been revoked.
revocation_reasonstringReason recorded when the API key was revoked.
secretstringAPI key secret value. Treat as high-privilege — do not log.
HTTP errors: clerk_connection_required, clerk_connection_not_found, clerk_connection_invalid, validation_error, unauthorized, payment_required