> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# messages | TON v3

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

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.

<Note>
  **TON billing: full (1 RU)**

  This method is always billed as full. See [Request units — TON method scope](/docs/request-units#ton-method-scope).
</Note>

## 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.


## OpenAPI

````yaml openapi/ton_node_api/v3/getMessages.json GET /messages
openapi: 3.0.0
info:
  title: TON API
  version: 3.0.0
  description: API for interacting with The Open Network (TON) blockchain
servers:
  - url: >-
      https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3
security: []
paths:
  /messages:
    get:
      tags:
        - Blockchain
      summary: Get Messages
      description: Retrieves a list of messages from the TON blockchain
      operationId: getMessages
      parameters:
        - name: limit
          in: query
          description: The maximum number of messages to return
          required: false
          schema:
            type: integer
            default: 128
        - name: offset
          in: query
          description: The number of messages to skip before starting to return results
          required: false
          schema:
            type: integer
            default: 0
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  messages:
                    type: array
                    items:
                      type: object
                      properties:
                        hash:
                          type: string
                          description: The message hash
                        source:
                          type: string
                          description: The source address of the message
                        destination:
                          type: string
                          description: The destination address of the message
                        value:
                          type: string
                          description: The value transferred in the message
                        fwd_fee:
                          type: string
                          description: The forward fee for the message
                        ihr_fee:
                          type: string
                          description: >-
                            The IHR (Instant Hypercube Routing) fee for the
                            message
                        created_lt:
                          type: string
                          description: The logical creation time of the message
                        body_hash:
                          type: string
                          description: The hash of the message body

````