Skip to main content
GET
Check OAuth API key existence

Authentication

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

Cache

No caching.

Notes

Use the decision matrix below to interpret the (exists, isEnabled) response and choose the next action.
  • Call the endpoint before redirecting the user to the OAuth authorization screen. Skipping the redirect when a key already exists avoids a flow the platform rejects.
  • Disabled keys are not deletable through the OAuth2 partner endpoint. Disabled keys are removed by the user from the WhiteBIT dashboard.
  • See Retrieve OAuth API key secret for the secret-fetch step and Delete OAuth API key for partner-initiated revocation.
  • The permissions array lists the permission groups the user granted on the consent screen — see Key permissions for the full permission model.

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

Response

Successful response

data
object