Trade Order Flow
How a request for a quote turns into a settled trade. Two API calls from you, then Bitrus settles asynchronously.
POST /quotes/ is binding for QUOTE_EXPIRATION_SECONDS (default 60s). Submit the trade order before expires_at or you will need to re-quote.Request a quote
POST /quotes/ — send the base asset, quote asset, side, and quantity. Bitrus returns a price binding for 60 seconds, plus an id you will pass to the order endpoint.
Request
curl -X POST https://api.bitrus.com/api/v1/quotes/ \
-H "Authorization: Bearer $BITRUS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"base_asset": "BTC",
"quote_asset": "USDT",
"quantity": "0.5",
"side": "BUY"
}'Response
1 keysCreate the trade order
POST /trade-order/ — pass the quote id and the network you want settlement on. The response includes the deposit address you must fund.
Request
curl -X POST https://api.bitrus.com/api/v1/trade-order/ \
-H "Authorization: Bearer $BITRUS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"quote_id": "ad5f2fa3-7f1b-4d0c-9d81-1f2c3cba9c01",
"network": "POLYGON"
}'Response
4 keysFund the deposit address
Send the exact quote total to the returned deposit address from your own wallet. Bitrus does not see the transfer until it confirms on chain.
Wait for settlement
The order moves through five statuses. Poll the order id, or rely on the operations email Bitrus sends on key transitions.
Statuses you will see
What each status means and what action, if any, it asks of you.
Need just the request and response shape?
The reference pages document every parameter, every response field, and every error these two endpoints can return.