messages | TON v3

The messages endpoint retrieves a list of messages from the TON blockchain. Chainstack supports messages on TON v3 JSON-RPC nodes.

GET /messages

Get Messages

cURL

curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/messages

200

{
  "messages": [
    {
      "hash": "<string>",
      "source": "<string>",
      "destination": "<string>",
      "value": "<string>",
      "fwd_fee": "<string>",
      "ihr_fee": "<string>",
      "created_lt": "<string>",
      "body_hash": "<string>"
    }
  ]
}

The messages endpoint retrieves a list of messages from the TON blockchain. This endpoint allows you to fetch recent messages and provides options for pagination.

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

TON billing: full (1 RU)

This method is always billed as full. See Request units — TON method scope.

Parameters

• limit (integer, optional) — The maximum number of messages to return. Default: 128.
• offset (integer, optional) — The number of messages to skip before starting to return results. Default: 0.

Response

• messages (array) — An array of message objects, each containing:
  • hash (string) — The message hash.
  • source (string) — The source address of the message.
  • destination (string) — The destination address of the message.
  • value (string) — The value transferred in the message.
  • fwd_fee (string) — The forward fee for the message.
  • ihr_fee (string) — The IHR (Instant Hypercube Routing) fee for the message.
  • created_lt (string) — The logical creation time of the message.
  • body_hash (string) — The hash of the message body.

Use case

The messages endpoint is useful for various applications that need to monitor or analyze message activity on the TON blockchain:

1. Block explorers can use this to display recent messages and allow users to browse through message history.
2. Wallet applications can fetch and display recent messages related to a user’s account.
3. Analytics tools can use this endpoint to gather data on message volumes, fees, and patterns over time.
4. Monitoring systems can track specific types of messages or activity between particular accounts.
5. Developers can use this endpoint to debug and verify message processing in smart contracts.

Query Parameters

limit · integer · default: 128

The maximum number of messages to return

offset · integer · default: 0

The number of messages to skip before starting to return results

Response

200 - application/json

Successful response

messages · object[]

Show child attributes