Access on behalf of a user

When to pass X-User-Wallet-Address and how the Broker wallet ownership check works.

When your Broker calls a private endpoint on behalf of a user, authenticate with your Broker API Key and identify the user with the X-User-Wallet-Address request header. The gateway verifies that the wallet belongs to your Broker. You do not need the user’s personal API Key or UID.

​

When to pass the wallet

Endpoint scope	X-User-Wallet-Address
DexBuilder asset-configuration queries	Not required
DexBuilder user, deposit, and withdrawal endpoints	Required
Prediction Markets and Event Contracts private REST endpoints	Required
Prediction Markets and Event Contracts public market data	Not required

Private order, position, and account requests use the Broker path prefixes in API conventions. A request is rejected if the wallet does not belong to the Broker or the Key lacks the required permission.

​

DexBuilder Platform endpoints

All paths below begin with /api/v4/dexbuilder. All require a Broker API Key and signature.

Group	Wallet	Endpoints
Asset configuration	Not required	GET /assets, /networks, /dw_status, /fee, /withdraw_limit
User	Required	GET /user/info, /wallet/list, /user/balance, /fund_stats
Deposit	Required	POST /deposit/fee, /deposit/sign_data; GET /deposit/status, /deposit/history
Withdrawal	Required	POST /withdraw/sign_data, /withdraw/submit, /withdraw/ata/check-and-build; GET /withdraw/status, /withdraw/history

Some endpoints require additional headers or Idempotency-Key; follow each endpoint page.

​

Example

GET /api/v4/dexbuilder/user/info HTTP/1.1
Host: api.dexbuilder.com
KEY: <BROKER_API_KEY>
Timestamp: <UNIX_SECONDS>
SIGN: <SIGN>
X-User-Wallet-Address: <USER_WALLET_ADDRESS>

X-User-Wallet-Address is not part of the REST signature string. See Broker API Key and signing. Private WebSocket channels identify the user according to their product-specific WebSocket documentation.