Convert - WhiteBIT

Convert provides instant currency conversion at a quoted rate. Unlike spot trading, Convert requires no orderbook interaction — request a quote, confirm before the quote expires, and the conversion executes immediately.

When to use Convert

Feature	Convert	Spot Trading
Execution	Instant at quoted rate	Depends on orderbook liquidity
Orderbook	No orderbook interaction	Orders placed on the orderbook
Order types	Single quote-and-confirm flow	6 order types (limit, market, stop-limit, stop-market, OCO, bulk)
Best for	Quick conversions, price estimation	Advanced trading strategies, precise price control

Convert also serves as a price estimation tool. Call the estimate endpoint before placing a market order to preview the approximate execution price.

Conversion flow

The conversion flow has two steps: estimate and confirm.

Request a quote

Send a POST request to /api/v4/convert/estimate with the following parameters: from (source ticker), to (destination ticker), direction ("from" or "to"), and amount. The response includes id (quote identifier), give, receive, rate, and expireAt.

Confirm the quote

Send a POST request to /api/v4/convert/confirm with quoteId set to the id returned by the estimate. The response returns finalGive and finalReceive.

Each estimate response includes an expireAt timestamp — confirm before that moment. Honour the value returned per quote rather than hard-coding a fixed window. If the quote expires before confirmation, request a new estimate.

API endpoints

Convert uses 3 authenticated endpoints. All require HMAC-SHA512 signing.

Endpoint	Purpose	Rate limit
`POST /api/v4/convert/estimate`	Request a conversion quote	10,000 req / 10 sec
`POST /api/v4/convert/confirm`	Confirm and execute a quote	10,000 req / 10 sec
`POST /api/v4/convert/history`	Retrieve conversion history (max 6 months)	10,000 req / 10 sec

Estimate parameters

Parameter	Type	Required	Description
`from`	string	Yes	Source currency ticker (e.g., `BTC`)
`to`	string	Yes	Destination currency ticker (e.g., `USDT`)
`direction`	string	Yes	`"from"` = amount is in source currency; `"to"` = amount is in destination currency
`amount`	string	Yes	Amount to convert or receive

Code example

Estimate a BTC-to-USDT conversion and confirm the quote.

cURL
Python

# Step 1: Request a conversion estimate
curl -X POST https://whitebit.com/api/v4/convert/estimate \
  -H "X-TXC-APIKEY: YOUR_API_KEY" \
  -H "X-TXC-PAYLOAD: YOUR_PAYLOAD" \
  -H "X-TXC-SIGNATURE: YOUR_SIGNATURE" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "BTC",
    "to": "USDT",
    "direction": "from",
    "amount": "1",
    "request": "/api/v4/convert/estimate",
    "nonce": 1
  }'

{
  "id": "123",
  "from": "BTC",
  "to": "USDT",
  "give": "1",
  "receive": "34299.76831549",
  "rate": "34299.76831549",
  "expireAt": 1699016476
}

# Step 2: Confirm the quote using the id from the estimate response
curl -X POST https://whitebit.com/api/v4/convert/confirm \
  -H "X-TXC-APIKEY: YOUR_API_KEY" \
  -H "X-TXC-PAYLOAD: YOUR_PAYLOAD" \
  -H "X-TXC-SIGNATURE: YOUR_SIGNATURE" \
  -H "Content-Type: application/json" \
  -d '{
    "quoteId": "123",
    "request": "/api/v4/convert/confirm",
    "nonce": 2
  }'

{
  "finalGive": "1",
  "finalReceive": "34299.76831549"
}

# Step 1: Request a conversion estimate.
# Request body for POST /api/v4/convert/estimate:
estimate_body = {
    "from": "BTC",
    "to": "USDT",
    "direction": "from",
    "amount": "1",
}
# The response returns id, give, receive, rate, and expireAt.

# Step 2: Confirm before expireAt, quoting the estimate id.
# Request body for POST /api/v4/convert/confirm:
confirm_body = {
    "quoteId": "123",  # id from the estimate response
}
# To send: add "request" and "nonce" to the body, serialize with compact
# separators (the server rejects spaced JSON), sign with HMAC-SHA512, and
# send with the X-TXC-APIKEY / X-TXC-PAYLOAD / X-TXC-SIGNATURE headers —
# implementation in the First API Call guide linked below.

First API Call documents the signing details (payload construction, nonce, and headers). For Go and PHP examples, see SDKs.

History filters

The history endpoint supports filtering by fromTicker, toTicker, quoteId, and time range (from/to timestamps). The default limit is 100 records. The maximum history depth is 6 months from the current month.

Convert in payment flows

Convert is commonly used as part of the withdrawal flow when the currency held in Main balance differs from the currency an end user needs to withdraw. The pattern is: request an estimate, confirm the quote, then submit the withdrawal in the destination currency — balance routing is handled internally by the convert service. For the full step-by-step withdrawal-with-conversion flow including code examples, see Payment Integration.

What’s next

Payment Integration

Deposit and withdrawal flows including conversion.

Spot Trading

Place orders on the orderbook with 6 order types.

WhiteBIT Codes

Transfer funds between accounts using fee-free digital vouchers.

​When to use Convert

​Conversion flow

​API endpoints

​Estimate parameters

​Code example

​History filters

​Convert in payment flows

​What’s next

Payment Integration

Spot Trading

WhiteBIT Codes

When to use Convert

Conversion flow

API endpoints

Estimate parameters

Code example

History filters

Convert in payment flows

What’s next