Travel Rule

Endpoint

Broker Withdraw (for brokers of local entities that require travel rule)

Submit a withdrawal request for brokers of local entities that required travel rule.

POST

/sapi/v1/localentity/broker/withdraw/apply

https://api.binance.com

Broker Withdraw (for brokers of local entities that require travel rule) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Broker Withdraw (for brokers of local entities that require travel rule) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight600

Broker Withdraw (for brokers of local entities that require travel rule) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Broker Withdraw (for brokers of local entities that require travel rule) › Request Body

address

string · required

Example: null

coin

string · required

Example: BTC

amount

number · float · required

Example: 1.0

withdrawOrderId

string · required

withdrawID defined by the client (i.e. client's internal withdrawID)

Example: 1

questionnaire

string · required

JSON format questionnaire answers.

Example: null

originatorPii

string · required

JSON format originator Pii, see StandardPii section below

Example: null

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

addressTag

string

Secondary address identifier for coins like XRP,XMR etc.

Example: null

network

string

Example: null

addressName

string

Description of the address. Address book cap is 200, space in name should be encoded into %20

Example: null

transactionFeeFlag

boolean

When making internal transfer, true for returning the fee to the destination account; false for returning the fee back to the departure account. Default false.

Example: true

walletType

integer · int64

The wallet type for withdraw，0-spot wallet ，1-funding wallet. Default walletType is the current "selected wallet" under wallet->Fiat and Spot/Funding->Deposit

Example: 0

Broker Withdraw (for brokers of local entities that require travel rule) › Responses

200

Broker Withdraw

trId

integer · int64

Example: 123456

accepted

boolean

Example: true

info

string

Example: Withdraw request accepted

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network)

This API will return user-specific Travel Rule questionnaire requirement information in reference to the current API key.

GET

/sapi/v1/localentity/questionnaire-requirements

https://api.binance.com

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Check Questionnaire Requirements (for local entities that require travel rule) (supporting network) › Responses

200

Check Questionnaire Requirements

questionnaireCountryCode

string

Example: AE

Get Country List

Query the active country list for travel rule questionnaires. Currently, only supports AU entity.

GET

/sapi/v1/localentity/country/list

https://api.binance.com

Get Country List › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Country List › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Country List › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Country List › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Country List › Responses

200

Country list

object[]

lastUpdated

integer · int64

Last data update timestamp (epoch milliseconds); 0 if empty.

Example: 1716300000000

Deposit History Travel Rule (for local entities that required travel rule) (supporting network)

Fetch deposit history for local entities that required travel rule.

GET

/sapi/v1/localentity/deposit/history

https://api.binance.com

Deposit History Travel Rule (for local entities that required travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Deposit History Travel Rule (for local entities that required travel rule) (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Deposit History Travel Rule (for local entities that required travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Deposit History Travel Rule (for local entities that required travel rule) (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

trId

string

Comma(,) separated list of travel rule record Ids.

Example: 1

txId

string

Comma(,) separated list of transaction Ids.

Example: 1

tranId

string

Comma(,) separated list of wallet tran Ids.

Example: 1

network

string

Example: null

coin

string

Example: BTC

travelRuleStatus

integer · int64

0,1,2

Example: 0

pendingQuestionnaire

boolean

true: Only return records that pending deposit questionnaire. false/not provided: return all records.

Example: true

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

offset

integer · int64

Default: 0

Example: null

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

Deposit History Travel Rule (for local entities that required travel rule) (supporting network) › Responses

200

Deposit History

object

trId

integer · int64

Example: 123451123

tranId

integer · int64

Example: 17644346245865

amount

string

Example: 0.001

coin

string

Example: BNB

network

string

Example: BNB

depositStatus

integer · int64

Example: 0

travelRuleStatus

integer · int64

Example: 1

travelRuleStatusV2

string

Overall travel rule verification status (GTR + sanctions screening combined). "PASSED": verification complete, deposit released. "PENDING": verification in progress, deposit frozen. "REJECTED": verification failed.

Example: PENDING

address

string

Example: bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23

addressTag

string

Example: 101764890

txId

string

Example: 98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC

insertTime

integer · int64

Example: 1661493146000

completeTime

integer · int64

Timestamp when the deposit was fully completed/credited (epoch ms).

Example: 1661493206000

transferType

integer · int64

Example: 0

confirmTimes

string

Example: 1/1

requireQuestionnaire

boolean

Example: false

questionnaire

string

Example: {"question1":"answer1","question2":"answer2"}

GET/sapi/v1/localentity/deposit/history

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/localentity/deposit/history?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

[
  {
    "trId": 123451123,
    "tranId": 17644346245865,
    "amount": "0.001",
    "coin": "BNB",
    "network": "BNB",
    "depositStatus": 0,
    "travelRuleStatus": 1,
    "travelRuleStatusV2": "PENDING",
    "address": "bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23",
    "addressTag": "101764890",
    "txId": "98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC",
    "insertTime": 1661493146000,
    "completeTime": 1661493206000,
    "transferType": 0,
    "confirmTimes": "1/1",
    "requireQuestionnaire": false,
    "questionnaire": "{\"question1\":\"answer1\",\"question2\":\"answer2\"}"
  }
]

json

application/json

Deposit History V2 (for local entities that required travel rule) (supporting network)

Fetch deposit history for local entities that with required travel rule information.

GET

/sapi/v2/localentity/deposit/history

https://api.binance.com

Deposit History V2 (for local entities that required travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Deposit History V2 (for local entities that required travel rule) (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Deposit History V2 (for local entities that required travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Deposit History V2 (for local entities that required travel rule) (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

depositId

integer · int64

Comma(,) separated list of wallet tran Ids.

Example: 1

txId

string

Comma(,) separated list of transaction Ids.

Example: 1

network

string

Example: null

coin

string

Example: BTC

retrieveQuestionnaire

boolean

true: return questionnaire within response.

Example: true

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

offset

integer · int64

Example: 0

Default: 0

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

Deposit History V2 (for local entities that required travel rule) (supporting network) › Responses

200

Deposit History V2

object

depositId

string

Example: 4615328107052018945

amount

string

Example: 0.01

network

string

Example: AVAXC

coin

string

Example: AVAX

depositStatus

integer · int64

Example: 1

travelRuleReqStatus

integer · int64

Example: 0

address

string

Example: 0x0010627ab66d69232f4080d54e0f838b4dc3894a

addressTag

string

Example:

txId

string

Example: 0xdde578983015741eed764e7ca10defb5a2caafdca3db5f92872d24a96beb1879

transferType

integer · int64

Example: 0

confirmTimes

string

Example: 12/12

requireQuestionnaire

boolean

Example: false

object

insertTime

integer · int64

Example: 1753053392000

Fetch address verification list

Fetch address verification list for user to check on status and other details for the addresses stored in Address Book.

GET

/sapi/v1/addressVerify/list

https://api.binance.com

Fetch address verification list › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Fetch address verification list › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Fetch address verification list › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Fetch address verification list › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Fetch address verification list › Responses

200

Fetch address verification list

object

status

string

Example: PENDING

token

string

Example: AVAX

network

string

Example: AVAXC

walletAddress

string

Example: 0xc03a6aa728a8dde7464c33828424ede7553a0021

object

Get Region List

Query the active region/city list for a given country. Currently, only supports AU entity.

GET

/sapi/v1/localentity/region/list

https://api.binance.com

Get Region List › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Region List › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Region List › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Region List › Query Parameters

countryCode

string · required

ISO 2-digit country code (from Country List API).

Example: au

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Region List › Responses

200

Region list

countryCode

string

Echoed country code (lowercase).

Example: au

object[]

lastUpdated

integer · int64

Last data update timestamp (epoch milliseconds); 0 if empty.

Example: 1716300000000

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network)

Submit questionnaire for brokers of local entities that require travel rule. The questionnaire is only applies to transactions from un-hosted wallets or VASPs that are not yet onboarded with GTR.

PUT

/sapi/v1/localentity/broker/deposit/provide-info

https://api.binance.com

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight600

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network) › Request Body

subAccountId

string · required

External user ID.

Example: 1

depositId

integer · int64 · required

Wallet deposit ID.

Example: 1

questionnaire

string · required

JSON format questionnaire answers.

Example: null

beneficiaryPii

string · required

JSON format beneficiary Pii.

Example: null

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

network

string

Example: null

coin

string

Example: BTC

amount

number · float

Example: 1.0

address

string

Example: null

addressTag

string

Example: null

Submit Deposit Questionnaire Broker (For local entities that require travel rule) (supporting network) › Responses

200

Submit Deposit Questionnaire

trId

integer · int64

Example: 765127651

accepted

boolean

Example: true

info

string

Example: Deposit questionnaire accepted.

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network)

Submit questionnaire for local entities that require travel rule. The questionnaire is only applies to transactions from unhosted wallets or VASPs that are not yet onboarded with GTR.

PUT

/sapi/v1/localentity/deposit/provide-info

https://api.binance.com

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight600

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) › Request Body

tranId

integer · int64 · required

Wallet tran ID

Example: 1

questionnaire

string · required

JSON format questionnaire answers.

Example: null

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Submit Deposit Questionnaire (For local entities that require travel rule) (supporting network) › Responses

200

Submit Deposit Questionnaire

trId

integer · int64

Example: 765127651

accepted

boolean

Example: true

info

string

Example: Deposit questionnaire accepted.

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network)

Submit questionnaire for local entities that require travel rule. The questionnaire is only applies to transactions from unhosted wallets or VASPs that are not yet onboarded with GTR.

PUT

/sapi/v2/localentity/deposit/provide-info

https://api.binance.com

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight600

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) › Request Body

depositId

integer · int64 · required

Wallet deposit ID

Example: 1

questionnaire

string · required

JSON format questionnaire answers.

Example: null

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Submit Deposit Questionnaire V2 (For local entities that require travel rule) (supporting network) › Responses

200

Submit Deposit Questionnaire V2

trId

integer · int64

Example: 765127651

accepted

boolean

Example: true

info

string

Example: Deposit questionnaire accepted.

VASP list (for local entities that require travel rule) (supporting network)

Fetch the VASP list for local entities.

GET

/sapi/v1/localentity/vasp

https://api.binance.com

VASP list (for local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

VASP list (for local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

VASP list (for local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

VASP list (for local entities that require travel rule) (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

VASP list (for local entities that require travel rule) (supporting network) › Responses

200

VASP list

object

vaspName

string

Example: Binance

vaspCode

string

Example: BINANCE

identifier

string

For populating the vasp field in the deposit/withdrawal questionnaire

Example: xxx

Withdraw History Travel Rule (supporting network)

Fetch withdraw history for local entities that required travel rule.

GET

/sapi/v1/localentity/withdraw/history

https://api.binance.com

Withdraw History Travel Rule (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Withdraw History Travel Rule (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Withdraw History Travel Rule (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Withdraw History Travel Rule (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

trId

string

Comma(,) separated list of travel rule record Ids.

Example: 1

txId

string

Comma(,) separated list of transaction Ids.

Example: 1

withdrawOrderId

string

client side id for withdrawal, if provided in POST /sapi/v1/capital/withdraw/apply, can be used here for query.

Example: 1

network

string

Example: null

coin

string

Example: BTC

travelRuleStatus

integer · int64

0,1,2

Example: 0

offset

integer · int64

Example: 0

Default: 0

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

recvWindow

integer · int64 · max: 60000

Example: 5000

Withdraw History Travel Rule (supporting network) › Responses

200

Withdraw History

object

id

string

Example: b6ae22b3aa844210a7041aee7589627c

trId

integer · int64

Example: 1234456

amount

string

Example: 8.91000000

transactionFee

string

Example: 0.004

coin

string

Example: USDT

withdrawalStatus

integer · int64

Example: 6

travelRuleStatus

integer · int64

Example: 0

address

string

Example: 0x94df8b352de7f46f64b01d3666bf6e936e44ce60

txId

string

Example: 0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268

applyTime

string

Example: 2019-10-12 11:12:02

network

string

Example: ETH

transferType

integer · int64

Example: 0

withdrawOrderId

string

Example: WITHDRAWtest123

info

string

Example: The address is not valid. Please confirm with the recipient

confirmNo

integer · int64

Example: 3

walletType

integer · int64

Example: 1

txKey

string

Example:

questionnaire

string

Example: {"question1":"answer1","question2":"answer2"}

completeTime

string

Example: 2023-03-23 16:52:41

GET/sapi/v1/localentity/withdraw/history

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/localentity/withdraw/history?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

[
  {
    "id": "b6ae22b3aa844210a7041aee7589627c",
    "trId": 1234456,
    "amount": "8.91000000",
    "transactionFee": "0.004",
    "coin": "USDT",
    "withdrawalStatus": 6,
    "travelRuleStatus": 0,
    "address": "0x94df8b352de7f46f64b01d3666bf6e936e44ce60",
    "txId": "0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268",
    "applyTime": "2019-10-12 11:12:02",
    "network": "ETH",
    "transferType": 0,
    "withdrawOrderId": "WITHDRAWtest123",
    "info": "The address is not valid. Please confirm with the recipient",
    "confirmNo": 3,
    "walletType": 1,
    "txKey": "",
    "questionnaire": "{\"question1\":\"answer1\",\"question2\":\"answer2\"}",
    "completeTime": "2023-03-23 16:52:41"
  }
]

json

application/json

Withdraw History V2 (for local entities that require travel rule) (supporting network)

Fetch withdraw history for local entities that required travel rule.

GET

/sapi/v2/localentity/withdraw/history

https://api.binance.com

Withdraw History V2 (for local entities that require travel rule) (supporting network) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Withdraw History V2 (for local entities that require travel rule) (supporting network) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Withdraw History V2 (for local entities that require travel rule) (supporting network) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Withdraw History V2 (for local entities that require travel rule) (supporting network) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

trId

string

Comma(,) separated list of travel rule record Ids.

Example: 1

txId

string

Comma(,) separated list of transaction Ids.

Example: 1

withdrawOrderId

string

client side id for withdrawal, if provided in POST /sapi/v1/capital/withdraw/apply, can be used here for query.

Example: 1

network

string

Example: null

coin

string

Example: null

travelRuleStatus

integer · int64

0,1,2

Example: 0

offset

integer · int64

Example: 0

Default: 0

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

recvWindow

integer · int64 · max: 60000

Example: 5000

Withdraw History V2 (for local entities that require travel rule) (supporting network) › Responses

200

Withdraw History V2

object

id

string

Example: b6ae22b3aa844210a7041aee7589627c

trId

integer · int64

Example: 1234456

amount

string

Example: 8.91000000

transactionFee

string

Example: 0.004

coin

string

Example: USDT

withdrawalStatus

integer · int64

Example: 6

travelRuleStatus

integer · int64

Example: 0

address

string

Example: 0x94df8b352de7f46f64b01d3666bf6e936e44ce60

txId

string

Example: 0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268

applyTime

string

Example: 2019-10-12 11:12:02

network

string

Example: ETH

transferType

integer · int64

Example: 0

withdrawOrderId

string

Example: WITHDRAWtest123

info

string

Example: The address is not valid. Please confirm with the recipient

confirmNo

integer · int64

Example: 3

walletType

integer · int64

Example: 1

txKey

string

Example:

questionnaire

string

Example: {"question1":"answer1","question2":"answer2"}

completeTime

string

Example: 2023-03-23 16:52:41

GET/sapi/v2/localentity/withdraw/history

curl --request GET \
  --url 'https://api.binance.com/sapi/v2/localentity/withdraw/history?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

[
  {
    "id": "b6ae22b3aa844210a7041aee7589627c",
    "trId": 1234456,
    "amount": "8.91000000",
    "transactionFee": "0.004",
    "coin": "USDT",
    "withdrawalStatus": 6,
    "travelRuleStatus": 0,
    "address": "0x94df8b352de7f46f64b01d3666bf6e936e44ce60",
    "txId": "0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268",
    "applyTime": "2019-10-12 11:12:02",
    "network": "ETH",
    "transferType": 0,
    "withdrawOrderId": "WITHDRAWtest123",
    "info": "The address is not valid. Please confirm with the recipient",
    "confirmNo": 3,
    "walletType": 1,
    "txKey": "",
    "questionnaire": "{\"question1\":\"answer1\",\"question2\":\"answer2\"}",
    "completeTime": "2023-03-23 16:52:41"
  }
]

json

application/json

Withdraw Travel Rule

Submit a withdrawal request for local entities that required travel rule.

POST

/sapi/v1/localentity/withdraw/apply

https://api.binance.com

Withdraw Travel Rule › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Withdraw Travel Rule › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight600

Withdraw Travel Rule › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Withdraw Travel Rule › Request Body

coin

string · required

Example: BTC

address

string · required

Withdrawal address

Example: null

amount

number · float · required

Amount

Example: 1.0

questionnaire

string · required

JSON format questionnaire answers.

Example: null

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

withdrawOrderId

string

withdrawID defined by the client (i.e. client's internal withdrawID)

Example: 1

network

string

Withdrawal network

Example: null

addressTag

string

Secondary address identifier for coins like XRP,XMR etc.

Example: null

transactionFeeFlag

boolean

When making internal transfer, true for returning the fee to the destination account; false for returning the fee back to the departure account. Default false.

Example: true

name

string

Example: null

walletType

integer · int64

The wallet type for withdraw，0-spot wallet ，1-funding wallet. Default walletType is the current "selected wallet" under wallet->Fiat and Spot/Funding->Deposit

Example: 0

recvWindow

integer · int64 · max: 60000

Example: 5000

Withdraw Travel Rule › Responses

200

Withdraw

trId

integer · int64

Example: 123456

accepted

boolean

Example: true

info

string

Example: Withdraw request accepted