Estimate deposit fees - DexBuilder Docs

curl --request POST \ --url https://api.dexbuilder.com/api/v4/dexbuilder/deposit/fee \ --header 'Content-Type: application/json' \ --header 'KEY: <api-key>' \ --header 'SIGN: <api-key>' \ --header 'Timestamp: <api-key>' \ --header 'X-User-Wallet-Address: <x-user-wallet-address>' \ --data ' { "address": "<string>", "chain": "ethereum", "token_address": "<string>", "token_amount": "<string>", "token_symbol": "<string>" } '

{ "code": 0, "message": "success", "reason": "<string>", "trace_id": "<string>", "data": { "deposit_fee": "<string>", "lz_fee": "<string>", "native_fee": 123, "fee_source": 123 } }

Usage notes

The request address must be the target user’s bound wallet. lz_fee is a USDT decimal string; convert it to an integer with six decimal places before calling Get deposit signing data, for example 0.5 becomes 500000. Pass native_fee unchanged as an integer in the chain’s smallest native unit.

fee_source=0 means a real-time quote; fee_source=1 means a fallback quote.

Authorizations

KEY

string

header

required

Broker API Key

Timestamp

string

header

required

Unix timestamp in seconds

SIGN

string

header

required

Hexadecimal HMAC-SHA512 signature generated with the Broker Secret Key

Headers

X-User-Wallet-Address

string

required

Target user's wallet address. The gateway verifies that the user belongs to the current Broker.

Body

application/json

address

string

required

Bound wallet initiating the deposit; EVM 0x hex or Solana base58

chain

enum<string>

required

Network identifier: base, bsc, ethereum, solana, or arbitrum.

Available options:

base,

bsc,

ethereum,

solana,

arbitrum

Example:

"ethereum"

token_address

string

required

Token contract; use the chain's designated zero address for a native token

token_amount

string

required

Deposit amount as a decimal string

token_symbol

string

required

Token symbol, such as USDT

Response

Query successful

code

integer

Business code; 0 indicates success

Example:

0

message

string

Human-readable message; success responses use success

Example:

"success"

reason

string

Error reason identifier; usually empty on success

trace_id

string

Trace ID to provide when requesting support

data

object

Show child attributes

{ "code": 0, "message": "success", "reason": "<string>", "trace_id": "<string>", "data": { "deposit_fee": "<string>", "lz_fee": "<string>", "native_fee": 123, "fee_source": 123 } }

​Usage notes

Authorizations

Headers

Body

Response

Usage notes