API Reference

Blink's integration is designed to be as simple as possible, it only requires switching over to Blink's RPC node endpoint.

This endpoint mirrors the APIs found by other BSC node providers, with Blink-specific methods layered on top.

You can find your custom endpoint on your custom dashboard.

Integration Steps

• Acquire custom RPC endpoint on our dashboard

• Switch out existing RPC endpoint for the custom Blink endpoint: https://bsc.blinklabs.xyz/v1/{$API_KEY}

• Track recoveries via Blink's dashboard

---

eth_sendRawTransaction

Blink will intercept eth_sendRawTransaction requests, it will;

• Bypass the public mempool

• Send the transaction directly to BSC builders

• Share the transaction with our searcher network and run the auction for it

Example request

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_sendRawTransaction",
    "params": [
        "0xf869018203e882520894f17f52151ebef6c7334fad080c5704d77216b732881bc16d674ec80000801ba02da1c48b670996dcb1f447ef9ef00b33033c48a4fe938f420bec3e56bfd24071a062e0aa78a81bf0290afbc3a9d8e9a068e6d74caa66c5e0fa8a46deaae96b0833",
     ],
}

Example response

{
    "id": 1,
    "jsonrpc": "2.0",
    "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}

---

eth_sendPrivateTransaction

Accepted as an alias of eth_sendRawTransaction, for compatibility with existing private transaction integrations. It takes the same signed raw transaction parameter and behaves identically — on BSC all Blink transactions bypass the public mempool regardless of which of the two methods you use.

Example request

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_sendPrivateTransaction",
    "params": [
        "0xf869018203e882520894f17f52151ebef6c7334fad080c5704d77216b732881bc16d674ec80000801ba02da1c48b670996dcb1f447ef9ef00b33033c48a4fe938f420bec3e56bfd24071a062e0aa78a81bf0290afbc3a9d8e9a068e6d74caa66c5e0fa8a46deaae96b0833",
     ],
}

---

eth_sendBundle

Note this is for originators who send transactions via bundles rather than searchers who are bundling with other transactions. Searchers bid on transactions through a separate endpoint and a different request shape — see Searchers.

Blink will intercept eth_sendBundle requests, it will;

• Bypass the public mempool

• Send the bundle directly to the BSC builders that accept bundles

• Share each transaction in the bundle with our searcher network and run the auction for it

Example request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_sendBundle",
  "params": [
    {
      txs,               // Array[String], A list of signed transactions to execute in an atomic bundle
    }
  ]
}

Example response

The result is the bundle hash, derived from the transactions in the bundle.

{
    "id": 1,
    "jsonrpc": "2.0",
    "result": "0x164d7d41f24b7f333af3b4a70b690cf93f636227165ea2b699fbb7eed09c46c7"
}

A bundle hash response acknowledges receipt only. Bundles are forwarded to builders asynchronously, so it does not confirm that the bundle reached a builder or landed on-chain.

Only txs is forwarded to BSC builders. blockNumber, revertingTxHashes, droppingTxHashes and the other Ethereum eth_sendBundle fields are accepted for compatibility but have no effect on BSC — in particular, a bundle cannot be pinned to a target block, and no transaction can be opted into reverting.

---

pm_isSponsorable

Used to check whether a transaction is eligible for gas sponsorship before signing it. See the Gas Sponsorship API Reference.

---

For full documentation of the remaining standard endpoints, we suggest referring to the BNB Chain documentation: https://docs.bnbchain.org/bnb-smart-chain/developers/json_rpc/json-rpc-endpoint/