Skip to main content
DELETE
Delete OAuth API key

Authentication

OAuth 2.0 Bearer token. Required scope: apikeys.delete. See Authentication. The endpoint is available on https://whitebit.com only.

Cache

No caching.

Notes

The endpoint deletes only OAuth-issued API keys owned by the authenticated OAuth2 client. Keys belonging to other OAuth2 clients return 403. Manually-created API keys are not deletable through this endpoint. Disabled keys (post-inactivity, awaiting user-side deletion) require user-initiated deletion from the WhiteBIT dashboard. Partner-initiated deletion through the endpoint triggers an email to the user. User-initiated dashboard deletion does not send an email.
  • Obtain the externalId path parameter from Check OAuth API key existence.
  • Automatic deletion triggers (14-day inactivity, account password change, account block, account freeze) also send an email to the user.

Used in these guides

  • Copy Trading — mirror a lead trader’s orders into followers’ own accounts via OAuth-issued keys.
  • Fast API Key integration — OAuth-issued API keys created on behalf of end users.

Authorizations

Authorization
string
header
required

OAuth 2.0 Bearer Token authentication. Include the access token in the Authorization header.

Example: Authorization: Bearer YOUR_ACCESS_TOKEN

Path Parameters

externalId
string<uuid>
required

External UUID of the API key.

Example:

"550e8400-e29b-41d4-a716-446655440000"

Response

Successful deletion.

data
any[]
Example: