DexBuilder Platform API authentication

Call DexBuilder Platform API endpoints at https://api.dexbuilder.com using the /api/v4/dexbuilder path prefix. Every endpoint requires KEY, Timestamp, and SIGN headers. See Broker API Key and signing. Your Broker API Key needs the dex_builder product permission. Read operations require read or read-write access; submission operations require read-write access. An end user’s personal API Key cannot replace a Broker API Key.

User wallet

Asset-configuration endpoints do not require X-User-Wallet-Address. User, deposit, and withdrawal endpoints require the target user’s wallet address in this header. The gateway verifies that the wallet belongs to your Broker. See Access on behalf of a user for the full list.

Device type

Some platform endpoints require the x-perp-device-type header. Supported values are 1 (Android), 2 (iOS), and 3 (WEB). 4 (H5) is not accepted by these DexBuilder Platform endpoints. Follow each endpoint’s required parameters. Withdrawal submission also requires Idempotency-Key. Other headers are specified on the relevant endpoint pages.

Example request

curl -i --request GET "https://api.dexbuilder.com/api/v4/dexbuilder/user/info" \
  --header "KEY: <BROKER_API_KEY>" \
  --header "SIGN: <SIGN>" \
  --header "Timestamp: <UNIX_SECONDS>" \
  --header "X-User-Wallet-Address: <USER_WALLET>" \
  --header "Accept: application/json"

Generate SIGN for the exact external path, method, query string, body, and timestamp that you send.

​User wallet

​Device type

​Example request

User wallet

Device type

Example request