Fiat REST API | Binance Developer Docs

Endpoint

Deposit

Submit deposit request, in this version, we only support BRL deposit via pix.

For BRL deposit via pix, you need to place an order before making a transfer from your bank.

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

POST

/sapi/v1/fiat/deposit

https://api.binance.com

Deposit › 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 › 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 Weight45000

Deposit › 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 › 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

Request validity window in milliseconds

Example: 5000

Deposit › Request Body

currency

string · required

Example: BRL

apiPaymentMethod

string · enum · required

payment method; current supported: pix

Enum values:

pix

Example: pix

amount

string · required

deposit amount

Example: 1

ext

object

Example: {}

Deposit › Responses

200

Deposit

code

string

Example: 000000

message

string

Example: success

object

Fiat Withdraw

Submit withdraw request, in this version, we support BRL,ARS,MXN withdrawal via bank_transfer.

You need to call this api first, and call query order detail api in a loop to get the status of the order until this order is successful.

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

POST

/sapi/v2/fiat/withdraw

https://api.binance.com

Fiat Withdraw › 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

Fiat Withdraw › 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 Weight45000

Fiat Withdraw › 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

Fiat Withdraw › 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

Request validity window in milliseconds

Example: 5000

Fiat Withdraw › Request Body

currency

string · required

Fiat currency, such as BRL, ARS, MXN

Example: BRL

apiPaymentMethod

string · enum · required

payment method; current supported: bank_transfer

Enum values:

bank_transfer

Example: bank_transfer

amount

integer · int64 · required

withdraw amount

Example: 10

object · required

withdraw account info

ext

object

Example: {}

Fiat Withdraw › Responses

200

Fiat Withdraw

code

string

Example: 000000

message

string

Example: success

object

Get Fiat Deposit/Withdraw History

GET

/sapi/v1/fiat/orders

https://api.binance.com

Get Fiat Deposit/Withdraw History › 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 Fiat Deposit/Withdraw History › 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 Weight45000

Get Fiat Deposit/Withdraw History › 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 Fiat Deposit/Withdraw History › Query Parameters

transactionType

string · required

0: deposit, 1: withdraw

Example: 0

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

beginTime

integer · int64

Example: 1641782889000

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

rows

integer · int64 · max: 500

Example: 100

Default: 100

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Fiat Deposit/Withdraw History › Responses

200

Get Fiat Deposit/Withdraw History

code

string

Example: 000000

message

string

Example: success

object[]

total

integer · int64

Example: 1

success

boolean

Example: true

Get Fiat Payments History

GET

/sapi/v1/fiat/payments

https://api.binance.com

Get Fiat Payments History › 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 Fiat Payments History › 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 Fiat Payments History › 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 Fiat Payments History › Query Parameters

transactionType

string · required

0: buy, 1: sell

Example: 0

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

beginTime

integer · int64

Example: 1641782889000

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

rows

integer · int64 · max: 500

Example: 100

Default: 100

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Fiat Payments History › Responses

200

Get Fiat Payments History

code

string

Example: 000000

message

string

Example: success

object[]

total

integer · int64

Example: 1

success

boolean

Example: true

Get Order Detail

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

GET

/sapi/v1/fiat/get-order-detail

https://api.binance.com

Get Order Detail › 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 Order Detail › 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 Order Detail › 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 Order Detail › Query Parameters

orderNo

string · required

Order ID retrieved from the withdrawal API

Example: 036752*678

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 Order Detail › Responses

200

Get Order Detail

code

string

Example: 000000

message

string

Example: success

object

Endpoint

Download schema

Deposit

Submit deposit request, in this version, we only support BRL deposit via pix.

For BRL deposit via pix, you need to place an order before making a transfer from your bank.

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

POST

/sapi/v1/fiat/deposit

https://api.binance.com

Deposit › 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 › 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 Weight45000

Deposit › 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 › 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

Request validity window in milliseconds

Example: 5000

Deposit › Request Body

currency

string · required

Example: BRL

apiPaymentMethod

string · enum · required

payment method; current supported: pix

Enum values:

pix

Example: pix

amount

string · required

deposit amount

Example: 1

ext

object

Example: {}

Deposit › Responses

200

Deposit

code

string

Example: 000000

message

string

Example: success

object

Fiat Withdraw

Submit withdraw request, in this version, we support BRL,ARS,MXN withdrawal via bank_transfer.

You need to call this api first, and call query order detail api in a loop to get the status of the order until this order is successful.

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

POST

/sapi/v2/fiat/withdraw

https://api.binance.com

Fiat Withdraw › 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

Fiat Withdraw › 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 Weight45000

Fiat Withdraw › 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

Fiat Withdraw › 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

Request validity window in milliseconds

Example: 5000

Fiat Withdraw › Request Body

currency

string · required

Fiat currency, such as BRL, ARS, MXN

Example: BRL

apiPaymentMethod

string · enum · required

payment method; current supported: bank_transfer

Enum values:

bank_transfer

Example: bank_transfer

amount

integer · int64 · required

withdraw amount

Example: 10

object · required

withdraw account info

ext

object

Example: {}

Fiat Withdraw › Responses

200

Fiat Withdraw

code

string

Example: 000000

message

string

Example: success

object

Get Fiat Deposit/Withdraw History

GET

/sapi/v1/fiat/orders

https://api.binance.com

Get Fiat Deposit/Withdraw History › 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 Fiat Deposit/Withdraw History › 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 Weight45000

Get Fiat Deposit/Withdraw History › 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 Fiat Deposit/Withdraw History › Query Parameters

transactionType

string · required

0: deposit, 1: withdraw

Example: 0

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

beginTime

integer · int64

Example: 1641782889000

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

rows

integer · int64 · max: 500

Example: 100

Default: 100

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Fiat Deposit/Withdraw History › Responses

200

Get Fiat Deposit/Withdraw History

code

string

Example: 000000

message

string

Example: success

object[]

total

integer · int64

Example: 1

success

boolean

Example: true

Get Fiat Payments History

GET

/sapi/v1/fiat/payments

https://api.binance.com

Get Fiat Payments History › 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 Fiat Payments History › 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 Fiat Payments History › 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 Fiat Payments History › Query Parameters

transactionType

string · required

0: buy, 1: sell

Example: 0

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

beginTime

integer · int64

Example: 1641782889000

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

rows

integer · int64 · max: 500

Example: 100

Default: 100

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Fiat Payments History › Responses

200

Get Fiat Payments History

code

string

Example: 000000

message

string

Example: success

object[]

total

integer · int64

Example: 1

success

boolean

Example: true

Get Order Detail

Before calling this api, please make sure you have already completed your KYC or KYB, and already activated your fiat service on our website.

GET

/sapi/v1/fiat/get-order-detail

https://api.binance.com

Get Order Detail › 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 Order Detail › 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 Order Detail › 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 Order Detail › Query Parameters

orderNo

string · required

Order ID retrieved from the withdrawal API

Example: 036752*678

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 Order Detail › Responses

200

Get Order Detail

code

string

Example: 000000

message

string

Example: success

object