Get deposit signing data - DexBuilder Docs

curl --request POST \ --url https://api.dexbuilder.com/api/v4/dexbuilder/deposit/sign_data \ --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>' \ --header 'x-perp-device-type: <x-perp-device-type>' \ --data ' { "address": "<string>", "chain": "ethereum", "token_address": "<string>", "token_amount": "<string>", "token_symbol": "<string>", "native_fee": 123, "lz_fee": 123 } '

{ "code": 0, "message": "success", "reason": "<string>", "trace_id": "<string>", "data": { "account_id": "<string>", "broker_hash": "<string>", "token_hash": "<string>", "token_amount": "<string>", "contract_address": "<string>", "data": "<string>" } }

Usage notes

First call Estimate deposit fees, pass native_fee unchanged, and convert lz_fee to an integer using six USDT decimal places.

A first successful call may bind the user’s Perp account; repeat calls do not bind it again. Use the returned contract_address and data to build the onchain transaction.

x-perp-device-type is required and accepts only 1, 2, or 3.

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.

x-perp-device-type

enum<string>

required

DexBuilder device type: 1 Android, 2 iOS, 3 WEB. A missing or invalid value returns INVALID_DEVICE_TYPE. Required only on the platform endpoints that specify this header.

Available options:

1,

2,

3

Body

application/json

address

string

required

Bound user wallet; must match X-User-Wallet-Address

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 address

token_amount

string

required

Deposit amount as a decimal string

token_symbol

string

required

Token symbol

native_fee

integer<int64>

native_fee from POST /deposit/fee, in the chain's smallest native unit as int64

lz_fee

integer<int64>

From POST /deposit/fee: convert the USDT decimal lz_fee to int64 with six decimal places (for example, 0.5 to 500000); pass native_fee unchanged as int64

Response

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

​Usage notes

Authorizations

Headers

Body

Response

Usage notes