BNB Beacon Chain

BNB Beacon Chain is a blockchain developed by Binance. With Tatum, you can access the most commonly used BNB Beacon Chain methods. These methods bring a certain level of abstraction and are used for applications that communicate with the blockchain directly.

BNB Beacon Chain does not provide the smart contract functionality.

Tatum supports the following BNB Beacon Chain networks:

  • Mainnet, the primary public production blockchain
  • Testnet, a chain used for testing purposes. The testnet cryptocurrency has no value, and you can obtain it from a faucet (for example, get it from the BNB Smart Chain Faucet and transfer it to your BNB Beacon Chain address using the Binance Wallet).

Generate Binance wallet

5 credits per API call.


Generate BNB account. Tatum does not support HD wallet for BNB, only specific address and private key can be generated.

SecurityX-API-Key
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/account
Request samples
Response samples
application/json
{
  • "address": "tbnb1sfj9981j2eo1ij2e09",
  • "privateKey": "cTmS2jBWXgFaXZ2xG9jhn67TiyTshnMp3UedamzEhGm6BZV1vLgQ"
}

Get Binance current block

5 credits per API call.


Get Binance current block number.

SecurityX-API-Key
Responses
200

OK

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/block/current
Request samples
Response samples
application/json
6491272

Get Binance Transactions in Block

5 credits per API call.


Get Transactions in block by block height.

SecurityX-API-Key
Request
path Parameters
height
required
number

Block height

Example: 6470657
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/block/{height}
Request samples
Response samples
application/json
{
  • "timestamp": 1651145988650,
  • "blockHeight": 44925860,
  • "tx": [
    ]
}

Get Binance Account

5 credits per API call.


Get Binance Account Detail by address.

SecurityX-API-Key
Request
path Parameters
address
required
string

Account address you want to get balance of

Example: tbnb185tqzq3j6y7yep85lncaz9qeectjxqe5054cgn
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/account/{address}
Request samples
Response samples
application/json
{
  • "account_number": 696215,
  • "address": "tbnb185tqzq3j6y7yep85lncaz9qeectjxqe5054cgn",
  • "balances": [
    ],
  • "flags": 0,
  • "sequence": 0
}

Get Binance Transaction

5 credits per API call.


Get Binance Transaction by transaction hash.

SecurityX-API-Key
Request
path Parameters
hash
required
string

Transaction hash

Example: 4B944BBF78F3ADE3A377551B5EA7AD0FEDBDA13165D932F94B106EF7A8E16C1A
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/transaction/{hash}
Request samples
Response samples
application/json
{
  • "code": 0,
  • "hash": "4B944BBF78F3ADE3A377551B5EA7AD0FEDBDA13165D932F94B106EF7A8E16C1A",
  • "height": "44925860",
  • "log": "Msg 0: ",
  • "ok": true,
  • "tx": {
    }
}

Get Binance Transactions By Address

5 credits per API call.


Get Binance Transactions by address.

SecurityX-API-Key
Request
path Parameters
address
required
string

Account address

Example: tbnb185tqzq3j6y7yep85lncaz9qeectjxqe5054cgn
query Parameters
startTime
required
number >= 0

Start time in milliseconds

Example: startTime=1651831727871
endTime
required
number >= 0

End time in milliseconds

Example: endTime=1651831727871
limit
number [ 1 .. 50 ]

Items per page.

Example: limit=10
offset
number >= 0

Pagination offset

Example: offset=10
asset
string

Asset name

Example: asset=BNB
addressType
string

Address type

Enum: "FROM" "TO"
Example: addressType=FROM
Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

get/v3/bnb/account/transaction/{address}
Request samples
Response samples
application/json
{
  • "total": 10,
  • "tx": [
    ]
}

Send Binance / Binance Token from account to account

10 credits per API call.


Send Binance or Binance Token token from account to account.

This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key. No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production, Tatum KMS should be used for the highest security standards, and signatureId should be present in the request. Alternatively, using the Tatum client library for supported languages.

SecurityX-API-Key
Request
Request Body schema: application/json
One of:
to
required
string [ 1 .. 100 ] characters

Blockchain address to send assets.

currency
required
string

Currency to transfer from Binance Blockchain Account.

Value: "BNB"
amount
required
string^[+]?((\d+(\.\d*)?)|(\.\d+))$

Amount to be sent in BNB.

fromPrivateKey
required
string [ 1 .. 100 ] characters

Private key of sender address.

message
string [ 1 .. 50 ] characters

Message to recipient.

Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

post/v3/bnb/transaction
Request samples
application/json
{
  • "to": "tbnb138u9djee6fwphhd2a3628q2h0j5w97yx48zqex",
  • "currency": "BNB",
  • "amount": "100000",
  • "fromPrivateKey": "cTmS2jBWXgFaXZ2xG9jhn67TiyTshnMp3UedamzEhGm6BZV1vLgQ"
}
Response samples
application/json
{
  • "txId": "c83f8818db43d9ba4accfe454aa44fc33123d47a4f89d47b314d6748eb0e9bc9"
}

Broadcast signed BNB transaction

5 credits per API call.


Broadcast signed transaction to Binance blockchain. This method is used internally or Tatum client libraries. It is possible to create custom signing mechanism and use this method only for broadcasting data to the blockchain.

SecurityX-API-Key
Request
Request Body schema: application/json
txData
required
string [ 1 .. 500000 ] characters

Raw signed transaction to be published to network.

signatureId
string = 24 characters

Identifier of KMS pending transaction ID to be completed with the broadcast.

Responses
200

OK

400

Bad Request. Validation failed for the given object in the HTTP Body or Request parameters.

401

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

403

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

500

Internal server error. There was an error on the server while processing the request.

post/v3/bnb/broadcast
Request samples
application/json
{
  • "txData": "62BD544D1B9031EFC330A3E855CC3A0D51CA5131455C1AB3BCAC6D243F65460D"
}
Response samples
application/json
{
  • "txId": "c83f8818db43d9ba4accfe454aa44fc33123d47a4f89d47b314d6748eb0e9bc9"
}