WhiteBIT OAuth API Keys API
Partner-facing endpoints for managing API keys created via the OAuth API key flow.Available on the global server (`https://whitebit.com`) only. The EU server (`https://whitebit.eu`) does not expose these endpoints in this release.Required scopes:- `apikeys.read` for `GET /oauth2/api-key/info` and `GET /oauth2/api-key/{externalId}/secret`- `apikeys.delete` for `DELETE /oauth2/api-key/{externalId}`A third scope, `apikeys.create`, authorizes key creation on the WhiteBIT consent screen and is not consumed by any endpoint here. Holding at least one of the three admits an OAuth2 client to the flow.
WhiteBIT OAuth API Keys API is one of 25 APIs that WhiteBIT publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 20 JSON Schema definitions.
Tagged areas include OAuth API Keys. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 20 JSON Schemas.
This API exposes 3 operations across 3 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 2 base URLs: https://whitebit.com, https://whitebit.eu.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
WhiteBIT OAuth API Keys API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
BearerAuth— OAuth 2.0 Bearer Token authentication. Include the access token in the Authorization header. Example: Authorization: Bearer YOURACCESSTOKEN
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 1 DELETE, 2 GET. Each is listed below with its method, path, parameters, and response codes.
Partner-facing endpoints for managing API keys created via the OAuth API key flow.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from WhiteBIT 12
Other APIs WhiteBIT publishes across the network.
This is an independent, third-party profile of WhiteBIT OAuth API Keys API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.