Destructive Pro

Revoke API Key

Permanently revokes exactly one API key, identified by its UUID or complete displayed prefix including the trailing '...' (for example, 'ws_abcdef123...'). Partial prefixes are rejected. Revocation is immediate and cannot be undone. It returns a not found error if the key does not belong to the current user.

revoke_api_keyDELETE/api/v1/api-keys/{key_id}
crispy — bash

Example prompt: Revoke the API key with displayed prefix ws_abcdef123... right now

{
  "revoked": true,
  "revoked_count": 1,
  "key_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "key_prefix": "ws_abcdef123..."
}
Permission scope
pro
Access
Destructive
Category
Account

What you can build

Immediately disable a leaked or compromised key
Free up a slot toward the 10-key limit before creating a new key
Retire a key tied to an integration you no longer use
Complete a credential rotation by removing the superseded key

Parameters

Inputs accepted by revoke_api_key.

NameTypeDescription
key_idstringThe key UUID (from list_api_keys) or complete displayed prefix including '...' (e.g. 'ws_abcdef123...'). Partial prefixes are rejected.

Run LinkedIn workflows from the AI client you already use.

Create your account, connect LinkedIn, create an API key, then add Crispy to your client. Review the docs for supported workflows and safety controls.