Retrieve OAuth API key secret
Retrieve OAuth API key secret
Retrieve the API secret for a partner-issued OAuth API key once. The secret is unrecoverable after retrieval.
GET
Retrieve OAuth API key secret
Authentication
OAuth 2.0 Bearer token. Required scope:apikeys.read. See Authentication. The endpoint is available on https://whitebit.com only.
Cache
No caching. The response carriesCache-Control: no-store.
Notes
The endpoint returns the secret exactly once per key. A subsequent call for the same key returns409 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.
- Obtain the
externalIdpath parameter from Check OAuth API key existence. - The endpoint does not return the public
apiKeystring. The WhiteBIT frontend delivers the publicapiKeyto the partner at consent completion. [PENDING: confirm with the WhiteBIT frontend team where exactly the partner receives the publicapiKey(callback parameter name and URL location) — update this note with the wire-level details once confirmed.]
Authorizations
OAuth 2.0 Bearer Token authentication. Include the access token in the Authorization header.
Example: Authorization: Bearer YOUR_ACCESS_TOKEN
Path Parameters
External UUID of the API key. Obtain the value from GET /oauth2/api-key/info.
Example:
"550e8400-e29b-41d4-a716-446655440000"
Response
Successful response. The secret is returned exactly once.