For the complete documentation index, see llms.txt. This page is also available as Markdown.

sendbocreturnhash - TON

Example code for the sendbocreturnhash JSON-RPC method. Сomplete guide on how to use sendbocreturnhash JSON-RPC in GetBlock.io Web3 documentation.

This method broadcasts a serialized BOC to the TON blockchain and returns the hash of the external message, allowing the caller to track its inclusion via tryLocateTx or getTransactions.

Parameters

Parameter
Type
Required
Description

boc

string

Yes

Base64-encoded BOC of the signed external message

Request Example

JSON-RPC (POST):

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "sendBocReturnHash",
    "params": {
        "boc": "te6cckEBAQEAUgAAn/8AIN0gggFMl7qXMO1E0NcLH+Ck8mCDCNcYINMf0x/THwL4I7vyZO1E0NMf0x/T//QE0VFDuvKhUVG68qIG+QFUEHb5EPKj+CO78mPtRNDXCx/jAFETuvKh1AAQc8L/8tCD"
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result.hash

string

Hash of the broadcast external message (base64), used for tracking

Use Cases

  • Broadcasting and tracking transfers in one step

  • Wallet UIs that display a pending tx hash immediately

  • Server-side automation that polls for inclusion

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

422

Validation Error

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

504

Lite Server Timeout

Upstream TON liteserver timed out

422

Validation Error

BOC payload is malformed or invalid base64

500

Liteserver rejected message

Message failed validity checks

SDK Integration

Last updated

Was this helpful?