Transaction API

Endpointhttps://web3.binance.com/build

Get Transaction Supported Chains

Return the blockchain networks supported by the Transaction service for gas estimation, simulation, and broadcasting. The list is dynamically configured server-side and may change over time.

GET

/api/v1/dex/pre-transaction/supported/chain

https://web3.binance.com/build

Get Transaction Supported Chains › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Transaction Supported Chains › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Transaction Supported Chains › Responses

Supported chains returned successfully.

code

integer · int32

Business status code. 0 indicates success; any non-zero value indicates a business error.

Example: 0

msg

string

Status description message.

Example: success

object[]

List of supported blockchain networks.

timestamp

integer · int64

Server response timestamp in milliseconds.

Example: 1748601600000

success

boolean

Convenience flag derived from code == 0.

Example: true

Get Gas Price

Query the current network gas price for the specified chain. The response shape varies by chain family:

EVM chains return both evmLegacyGasPrice (legacy gasPrice) and eip1559GasPrice (baseFee + priority/max fees) when EIP-1559 is supported.
Solana returns solanaGasPrice (compute-unit prices and Jito tips). Fields not applicable to the chain family are returned as null.

GET

/api/v1/dex/pre-transaction/gas-price

https://web3.binance.com/build

Get Gas Price › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Gas Price › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Gas Price › Query Parameters

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

Get Gas Price › Responses

Current gas price for the specified chain.

code

integer · int32

Business status code. 0 indicates success.

Example: 0

msg

string

Example: success

object

Gas price details. Populated fields depend on chain family.

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

GET/api/v1/dex/pre-transaction/gas-price

curl --request GET \
  --url 'https://web3.binance.com/build/api/v1/dex/pre-transaction/gas-price?binanceChainId=%3Cstring%3E' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>'

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "evmLegacyGasPrice": {
      "lowGasPrice": "1000000000",
      "mediumGasPrice": "2000000000",
      "highGasPrice": "5000000000"
    },
    "eip1559GasPrice": {
      "baseFee": "1500000000",
      "lowPriorityFee": "100000000",
      "lowMaxFee": "1700000000",
      "mediumPriorityFee": "500000000",
      "mediumMaxFee": "2200000000",
      "highPriorityFee": "1000000000",
      "highMaxFee": "3000000000"
    },
    "solanaGasPrice": {
      "lowComputeUnitPrice": "500",
      "lowJitoTip": "10000",
      "mediumComputeUnitPrice": "1000",
      "mediumJitoTip": "50000",
      "highComputeUnitPrice": "5000",
      "highJitoTip": "200000"
    }
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Get Gas Limit

Estimate the gas limit (or compute-unit ceiling on Solana) for an unsigned transaction. Provide either evmTx for EVM chains or solTx for Solana, matching the value of binanceChainId.

POST

/api/v1/dex/pre-transaction/gas-limit

https://web3.binance.com/build

Get Gas Limit › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Gas Limit › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Gas Limit › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

object

EVM transaction payload. Required when binanceChainId belongs to an EVM chain.

object

Solana transaction payload. Required when binanceChainId=CT_501.

Get Gas Limit › Responses

Estimated gas limit.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

Simulate Transactions

Simulate transaction execution off-chain to predict its outcome before broadcasting. The response includes the predicted execution status, balance changes per affected account/token, and ERC-20 allowance changes (EVM chains). Provide either evmTx (EVM chains) or solTx (Solana) matching binanceChainId.

POST

/api/v1/dex/pre-transaction/simulate

https://web3.binance.com/build

Simulate Transactions › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Simulate Transactions › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Simulate Transactions › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

object

EVM transaction payload. Required when binanceChainId belongs to an EVM chain.

object

Solana transaction payload. Required when binanceChainId=CT_501.

Simulate Transactions › Responses

Simulation result.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

POST/api/v1/dex/pre-transaction/simulate

curl --request POST \
  --url https://web3.binance.com/build/api/v1/dex/pre-transaction/simulate \
  --header 'Content-Type: application/json' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>' \
  --data '
{
  "binanceChainId": "1"
}
'

Example Request Body

{
  "binanceChainId": "1"
}

json

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "status": "SUCCESS",
    "failReason": "execution reverted: ERC20InsufficientBalance",
    "balanceChanges": [
      {
        "contractAddress": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
        "tokenType": "ERC20",
        "change": "-1000000",
        "owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
      }
    ],
    "allowanceChanges": [
      {
        "tokenAddress": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
        "owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "spender": "0x1111111254EEB25477B68fb85Ed929f73A960582",
        "preAmount": "0",
        "postAmount": "1000000"
      }
    ]
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Broadcast Transactions

Broadcast a client-signed transaction to the chain via the Binance Web3 API relay. Returns the transaction hash and an internal orderId you can use to track on-chain status via the post-transaction service. Optional MEV protection (EVM chains only) routes the transaction through a private mempool to mitigate front-running and sandwich attacks.

POST

/api/v1/dex/pre-transaction/broadcast-transaction

https://web3.binance.com/build

Broadcast Transactions › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Broadcast Transactions › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Broadcast Transactions › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

signedTransaction

string · required

Client-signed raw transaction. EVM chains use a hex-encoded RLP transaction; Solana uses a base64-encoded signed transaction.

Example: 0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...

address

string · required

Sender wallet address. Used for status attribution and signature verification.

Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

enableMevProtection

boolean

When true, route the transaction through a private mempool for MEV protection.

Example: false

Broadcast Transactions › Responses

Transaction submitted successfully.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

POST/api/v1/dex/pre-transaction/broadcast-transaction

curl --request POST \
  --url https://web3.binance.com/build/api/v1/dex/pre-transaction/broadcast-transaction \
  --header 'Content-Type: application/json' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>' \
  --data '
{
  "binanceChainId": "1",
  "signedTransaction": "0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
'

Example Request Body

{
  "binanceChainId": "1",
  "signedTransaction": "0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}

json

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "orderId": "1812345678901234567",
    "txHash": "0xabc123def4567890abc123def4567890abc123def4567890abc123def4567890"
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Get Broadcast Orders

Look up broadcast orders previously submitted via /pre-transaction/broadcast-transaction. Filter by txStatus or orderId, paginate with cursor.

GET

/api/v1/dex/post-transaction/orders

https://web3.binance.com/build

Get Broadcast Orders › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Broadcast Orders › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Broadcast Orders › Query Parameters

address

string · required

Sender wallet address whose orders to list.

Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

txStatus

string

Optional filter on transaction status (server-defined string, e.g. "pending", "success", "fail").

Example: success

orderId

string

Optional filter to fetch a single order by its internal order ID.

Example: 1812345678901234567

cursor

string

Pagination cursor returned by the previous page. Omit on the first request.

Example: eyJ0aW1lIjoxNzQ4NjAwMDAwMDAwLCJpZCI6MTIzfQ==

limit

integer · int32

Page size. Defaults to 20.

Example: 20

Default: 20

Get Broadcast Orders › Responses

Orders returned successfully.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

GET/api/v1/dex/post-transaction/orders

curl --request GET \
  --url 'https://web3.binance.com/build/api/v1/dex/post-transaction/orders?address=%3Cstring%3E&binanceChainId=%3Cstring%3E' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>'

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "cursor": "eyJ0aW1lIjoxNzQ4NTk5MDAwMDAwLCJpZCI6Nzh9",
    "orders": [
      {
        "orderId": "1812345678901234567",
        "binanceChainId": "1",
        "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "txHash": "0xabc123def4567890abc123def4567890abc123def4567890abc123def4567890",
        "txStatus": "success",
        "failReason": "execution reverted: insufficient liquidity"
      }
    ]
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Transaction API

Endpointhttps://web3.binance.com/build

Download schema

Get Transaction Supported Chains

Return the blockchain networks supported by the Transaction service for gas estimation, simulation, and broadcasting. The list is dynamically configured server-side and may change over time.

GET

/api/v1/dex/pre-transaction/supported/chain

https://web3.binance.com/build

Get Transaction Supported Chains › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Transaction Supported Chains › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Transaction Supported Chains › Responses

Supported chains returned successfully.

code

integer · int32

Business status code. 0 indicates success; any non-zero value indicates a business error.

Example: 0

msg

string

Status description message.

Example: success

object[]

List of supported blockchain networks.

timestamp

integer · int64

Server response timestamp in milliseconds.

Example: 1748601600000

success

boolean

Convenience flag derived from code == 0.

Example: true

Get Gas Price

Query the current network gas price for the specified chain. The response shape varies by chain family:

EVM chains return both evmLegacyGasPrice (legacy gasPrice) and eip1559GasPrice (baseFee + priority/max fees) when EIP-1559 is supported.
Solana returns solanaGasPrice (compute-unit prices and Jito tips). Fields not applicable to the chain family are returned as null.

GET

/api/v1/dex/pre-transaction/gas-price

https://web3.binance.com/build

Get Gas Price › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Gas Price › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Gas Price › Query Parameters

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

Get Gas Price › Responses

Current gas price for the specified chain.

code

integer · int32

Business status code. 0 indicates success.

Example: 0

msg

string

Example: success

object

Gas price details. Populated fields depend on chain family.

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

GET/api/v1/dex/pre-transaction/gas-price

curl --request GET \
  --url 'https://web3.binance.com/build/api/v1/dex/pre-transaction/gas-price?binanceChainId=%3Cstring%3E' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>'

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "evmLegacyGasPrice": {
      "lowGasPrice": "1000000000",
      "mediumGasPrice": "2000000000",
      "highGasPrice": "5000000000"
    },
    "eip1559GasPrice": {
      "baseFee": "1500000000",
      "lowPriorityFee": "100000000",
      "lowMaxFee": "1700000000",
      "mediumPriorityFee": "500000000",
      "mediumMaxFee": "2200000000",
      "highPriorityFee": "1000000000",
      "highMaxFee": "3000000000"
    },
    "solanaGasPrice": {
      "lowComputeUnitPrice": "500",
      "lowJitoTip": "10000",
      "mediumComputeUnitPrice": "1000",
      "mediumJitoTip": "50000",
      "highComputeUnitPrice": "5000",
      "highJitoTip": "200000"
    }
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Get Gas Limit

Estimate the gas limit (or compute-unit ceiling on Solana) for an unsigned transaction. Provide either evmTx for EVM chains or solTx for Solana, matching the value of binanceChainId.

POST

/api/v1/dex/pre-transaction/gas-limit

https://web3.binance.com/build

Get Gas Limit › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Gas Limit › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Gas Limit › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

object

EVM transaction payload. Required when binanceChainId belongs to an EVM chain.

object

Solana transaction payload. Required when binanceChainId=CT_501.

Get Gas Limit › Responses

Estimated gas limit.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

Simulate Transactions

POST

/api/v1/dex/pre-transaction/simulate

https://web3.binance.com/build

Simulate Transactions › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Simulate Transactions › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Simulate Transactions › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

object

EVM transaction payload. Required when binanceChainId belongs to an EVM chain.

object

Solana transaction payload. Required when binanceChainId=CT_501.

Simulate Transactions › Responses

Simulation result.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

POST/api/v1/dex/pre-transaction/simulate

curl --request POST \
  --url https://web3.binance.com/build/api/v1/dex/pre-transaction/simulate \
  --header 'Content-Type: application/json' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>' \
  --data '
{
  "binanceChainId": "1"
}
'

Example Request Body

{
  "binanceChainId": "1"
}

json

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "status": "SUCCESS",
    "failReason": "execution reverted: ERC20InsufficientBalance",
    "balanceChanges": [
      {
        "contractAddress": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
        "tokenType": "ERC20",
        "change": "-1000000",
        "owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
      }
    ],
    "allowanceChanges": [
      {
        "tokenAddress": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
        "owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "spender": "0x1111111254EEB25477B68fb85Ed929f73A960582",
        "preAmount": "0",
        "postAmount": "1000000"
      }
    ]
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Broadcast Transactions

POST

/api/v1/dex/pre-transaction/broadcast-transaction

https://web3.binance.com/build

Broadcast Transactions › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Broadcast Transactions › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Broadcast Transactions › Request Body

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

signedTransaction

string · required

Client-signed raw transaction. EVM chains use a hex-encoded RLP transaction; Solana uses a base64-encoded signed transaction.

Example: 0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...

address

string · required

Sender wallet address. Used for status attribution and signature verification.

Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

enableMevProtection

boolean

When true, route the transaction through a private mempool for MEV protection.

Example: false

Broadcast Transactions › Responses

Transaction submitted successfully.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

POST/api/v1/dex/pre-transaction/broadcast-transaction

curl --request POST \
  --url https://web3.binance.com/build/api/v1/dex/pre-transaction/broadcast-transaction \
  --header 'Content-Type: application/json' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>' \
  --data '
{
  "binanceChainId": "1",
  "signedTransaction": "0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
'

Example Request Body

{
  "binanceChainId": "1",
  "signedTransaction": "0xf86c808504a817c80082520894d8da6bf26964af9d7eed9e03e53415d37aa96045880de0b6b3a76400008025a0...",
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}

json

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "orderId": "1812345678901234567",
    "txHash": "0xabc123def4567890abc123def4567890abc123def4567890abc123def4567890"
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json

Get Broadcast Orders

Look up broadcast orders previously submitted via /pre-transaction/broadcast-transaction. Filter by txStatus or orderId, paginate with cursor.

GET

/api/v1/dex/post-transaction/orders

https://web3.binance.com/build

Get Broadcast Orders › Authorization

This is a signed endpoint and a signature must be included in the request headers.Learn more about how to generate a valid signature in the Authentication.

Get Broadcast Orders › Headers

X-OC-APIKEY

string · required

API Key issued by Binance Web3 API for authentication.

Example: your-api-key-here

X-OC-TIMESTAMP

string · required

Current UTC time in ISO 8601 format with milliseconds, e.g. 2026-05-11T10:08:57.715Z.

Example: 2026-05-11T10:08:57.715Z

X-OC-SIGN

string · required

Request signature (Base64-encoded).

Example: Base64EncodedSignature==

X-OC-RECV-WINDOW

integer · int64

Allowed time deviation in milliseconds (default: 5000, max: 60000).

Example: 5000

X-OC-NONCE

string

Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

Example: unique-nonce-string

Get Broadcast Orders › Query Parameters

address

string · required

Sender wallet address whose orders to list.

Example: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

binanceChainId

string · required

Unique chain identifier (e.g. "1"=Ethereum, "56"=BSC, "CT_501"=Solana).

Example: 1

txStatus

string

Optional filter on transaction status (server-defined string, e.g. "pending", "success", "fail").

Example: success

orderId

string

Optional filter to fetch a single order by its internal order ID.

Example: 1812345678901234567

cursor

string

Pagination cursor returned by the previous page. Omit on the first request.

Example: eyJ0aW1lIjoxNzQ4NjAwMDAwMDAwLCJpZCI6MTIzfQ==

limit

integer · int32

Page size. Defaults to 20.

Example: 20

Default: 20

Get Broadcast Orders › Responses

Orders returned successfully.

code

integer · int32

Example: 0

msg

string

Example: success

object

timestamp

integer · int64

Example: 1748601600000

success

boolean

Example: true

GET/api/v1/dex/post-transaction/orders

curl --request GET \
  --url 'https://web3.binance.com/build/api/v1/dex/post-transaction/orders?address=%3Cstring%3E&binanceChainId=%3Cstring%3E' \
  --header 'X-OC-APIKEY: <string>' \
  --header 'X-OC-SIGN: <string>' \
  --header 'X-OC-TIMESTAMP: <string>'

Example Responses

{
  "code": 0,
  "msg": "success",
  "data": {
    "cursor": "eyJ0aW1lIjoxNzQ4NTk5MDAwMDAwLCJpZCI6Nzh9",
    "orders": [
      {
        "orderId": "1812345678901234567",
        "binanceChainId": "1",
        "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "txHash": "0xabc123def4567890abc123def4567890abc123def4567890abc123def4567890",
        "txStatus": "success",
        "failReason": "execution reverted: insufficient liquidity"
      }
    ]
  },
  "timestamp": 1748601600000,
  "success": true
}

json

application/json