Retrieve the API secret for a partner-issued OAuth API key once. The secret is unrecoverable after retrieval.
Documentation Index
Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
Use this file to discover all available pages before exploring further.
apikeys.read. See Authentication. The endpoint is available on https://whitebit.com only.
Cache-Control: no-store.
409 Conflict. Recovery from 409 requires deleting the key via Delete OAuth API key and restarting the OAuth API key flow to issue a new key — the secret cannot be re-issued for an existing key.
A 423 Locked response indicates a concurrent secret-retrieval attempt against the same key. Retry the request after a short delay. Use exponential backoff starting at 5–10 seconds, doubling per attempt, capped at 60 seconds, with a total budget of 3–5 minutes. The platform does not currently send a Retry-After header.
externalId path parameter from Check OAuth API key existence.apiKey string. The WhiteBIT frontend delivers the public apiKey to the partner at consent completion. [PENDING: confirm with the WhiteBIT frontend team where exactly the partner receives the public apiKey (callback parameter name and URL location) — update this note with the wire-level details once confirmed.]OAuth 2.0 Bearer Token authentication. Include the access token in the Authorization header.
Example: Authorization: Bearer YOUR_ACCESS_TOKEN
External UUID of the API key. Obtain the value from GET /oauth2/api-key/info.
"550e8400-e29b-41d4-a716-446655440000"
Successful response. The secret is returned exactly once.