Transfer Funds

Transfer USDT between supported accounts and the Event Contracts account.

POST /api/v4/broker/event_contracts/transfer

Transfer Event Contract Funds

cURL

curl --request POST \
  --url https://api.dexbuilder.com/api/v4/broker/event_contracts/transfer \
  --header 'Content-Type: application/json' \
  --header 'KEY: <api-key>' \
  --header 'SIGN: <sign>' \
  --header 'Timestamp: <timestamp>' \
  --header 'X-User-Wallet-Address: <x-user-wallet-address>' \
  --data '
{
  "currency": "USDT",
  "amount": "<string>",
  "client_oid": "<string>"
}
'

200

{
  "amount": "1.2",
  "currency": "USDT",
  "from_account": "spot",
  "status": "SUCCESS",
  "to_account": "sub_spot",
  "transfer_id": "123"
}

Transfers USDT between a supported account and the product account.

Base URL: https://api.dexbuilder.com

Authentication: Use a Broker API Key and sign this request with Timestamp and SIGN. Pass a wallet address that belongs to your Broker in X-User-Wallet-Address. Calculate the signature using the external Broker path. See Broker API Key and signing and Access on behalf of a user.

​

Request

curl -X POST "https://api.dexbuilder.com/api/v4/broker/event_contracts/transfer" \
  -H "KEY: ${BROKER_API_KEY}" \
  -H "SIGN: ${SIGN}" \
  -H "Timestamp: ${TIMESTAMP}" \
  -H "X-User-Wallet-Address: ${USER_WALLET}" \
  -H "Content-Type: application/json" \
  -d '<request-body>'

The request body specifies the transfer direction and amount. Review the OpenAPI schema for required fields.

The OpenAPI panel below is the source of truth for required parameters, types, enum values, and request-body fields. Timestamps are Unix timestamps unless the field description states otherwise.

​

Response

Returns the transfer request status and identifiers. Verify the resulting balance and fund-flow record.

A successful response uses HTTP 200. Invalid parameters or request bodies return HTTP 400. Private endpoints can return HTTP 401 when authentication fails, and temporary upstream failures can return HTTP 503. The error response contains a machine-readable label and message.

For order, position, claim, transfer, and account operations, treat the response as the current server result and query the resource again when the operation is asynchronous.

Authorizations

KEY · string · header · required

Broker API Key, created through the project administrator's process.

Headers

Timestamp · string · required

Unix timestamp in seconds; the gateway allows at most 60 seconds of clock skew.

SIGN · string · required

Hexadecimal HMAC-SHA512 signature over the external request path, query string, and body.

X-User-Wallet-Address · string · required

End-user wallet address. The gateway checks that this wallet belongs to the current Broker.

Body

application/json

from_account · enum<string> · required

Available options: spot, sub_spot, event_contract

to_account · enum<string> · required

Available options: spot, sub_spot, event_contract

currency · enum<string> · required

Available options: USDT

amount · string · required

client_oid · string · required

Response

200

application/json

Request succeeded

Response object.

amount · string

Example:

"1.2"

currency · enum<string>

Available options: USDT

Example:

"USDT"

from_account · enum<string>

Available options: spot, sub_spot

Example:

"spot"

status · enum<string>

Available options: SUCCESS

Example:

"SUCCESS"

to_account · enum<string>

Available options: spot, sub_spot

Example:

"sub_spot"

transfer_id · string

Example:

"123"