Public API V1 Documentation - General endpoints
Public API V2 Documentation - Endpoints for cmc
Public API V4 Documentation - Additional endpoints
Private API Authentication Documentation - Documentation for making private Auth requests on WhiteBIT
Private API V1 Documentation Trade keys - Documentations for making private trading requests
Private API V4 Documentation Trade keys - Documentations for making private trading requests
Private API V4 Documentation Deposit/Withdraw keys - Documentations for making private trading & deposit/withdraw requests
Documentation for WebHooks - Documentations for processing web-hooks
- WhiteBIT API supports
private
andpublic
methods. - Available API versions:
V1
,V2
,V4
. - Using Public endpoints:
- Public endpoints are cached. You can find specific cache refresh interval for each particular request in API documentation.
- Use HTTP method
GET
method when making a request. - Use
query string
if you need to send additional data.
- Using Private endpoints:
- To make private API calls:
- Go to your account on whitebit.com.
- Click on the API keys tab.
- Select the appropriate configuration tab for your API keys. Different API keys allow access to different API calls.
- Generate API keys and toggle the activation switcher to "Activated".
- Auth request should be using
POST
method and should include:- Body data - JSON that includes:
- 'request' - a request path without the domain name. Example:
'/api/v4/trade-account/balance'
. - 'nonce' - a number that is always larger than the previous request’s nonce number. Example:
'1594297865'
. A good method of creating a nonce is to use the unix timestamp in milliseconds. This way you'll always get an incrementing number, but make sure not to send two API calls at the same time, otherwise their nonce will be identical. - params of request - Example:
'ticker': 'BTC'
- 'request' - a request path without the domain name. Example:
- Headers:
'Content-type': 'application/json'
'X-TXC-APIKEY': api_key
- where api_key is your public WhiteBit API key'X-TXC-PAYLOAD': payload'
- where payload is base64-encoded body data'X-TXC-SIGNATURE': signature
- where signature ishex(HMAC_SHA512(payload), key=api_secret))
- Body data - JSON that includes:
- To help you get started with our API, we've created the API Quick start helper library. It supports the following languages:
Go
NodeJS
Python
PHP
Java
Kotlin
DotNet
Ruby
C++
- To make private API calls: