Send BSC / BEP20 from account to account

post

https://api.tatum.io/v3/bsc/transaction

/v3/bsc/transaction

2 credits per API call

Send BNB or Tatum supported BEP20 token from account to account.

Signing a transaction

When sending BNB, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.

Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.

For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

data

string

length ≤ 50000

(Only for BSC transactions) Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format

nonce

number

≥ 0

Nonce to be set to BSC transaction. If not present, last known nonce will be used.

string

required

length between 42 and 42

Blockchain address to send assets

currency

string

enum

required

Currency to transfer from BSC Blockchain Account. BEP20 tokens like BETH, BBTC, BADA, WBNB, BDOT, BXRP, BLTC, BBCH, CAKE are available only for mainnet use.

fee

object

The custom defined fee; if not present, will be calculated automatically

amount

string

required

Amount to be sent.

fromPrivateKey

string

required

length between 66 and 66

Private key of sender address. Private key, or signature Id must be present.

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200OK

400Bad Request

401Unauthorized. Not valid or inactive subscription key present in the HTTP Header.

403Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.

500Internal server error. There was an error on the server during the processing of the request.