> ## Documentation Index
> Fetch the complete documentation index at: https://chainstack-docs-polygon-erigon-trace-deprecation.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# transactionsByMessage | TON v3

> The transactionsByMessage endpoint retrieves a list of transactions related to a specific message in the TON blockchain. On TON v3.

The `transactionsByMessage` endpoint retrieves a list of transactions related to a specific message in the TON blockchain. This endpoint allows you to fetch transactions associated with a particular message hash 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

* `direction` (string, required) — The direction of the message. Possible values: `in` or `out`. Default: `out`.
* `msg_hash` (string, required) — The hash of the message. Example: `po4/F9OgHrJGTUCtobScZrW/gOwVPj7s3f40HV32EII=`.
* `limit` (integer, optional) — The maximum number of transactions to return. Default: `128`.
* `offset` (integer, optional) — The number of transactions to skip before starting to return results. Default: `0`.

## Response

* `transactions` (array) — An array of transaction objects, each containing:
  * `hash` (string) — The transaction hash.
  * `lt` (string) — The logical time of the transaction.
  * `account` (string) — The account address involved in the transaction.
  * `now` (integer) — The timestamp of the transaction.
  * `origStatus` (string) — The original status of the account.
  * `endStatus` (string) — The end status of the account.
  * `totalFees` (string) — The total fees for the transaction.

## Use case

The `transactionsByMessage` endpoint is useful for various applications that need to track or analyze specific messages and their related transactions:

1. Wallet applications can use this to track the status of sent or received messages and their associated transactions.
2. Block explorers can provide detailed information about message propagation and the resulting transactions.
3. Developers can use this endpoint to debug and verify message processing in smart contracts.
4. Analytics tools can track the impact of specific messages on the blockchain state.


## OpenAPI

````yaml openapi/ton_node_api/v3/getTransactionsByMessage.json GET /transactionsByMessage
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:
  /transactionsByMessage:
    get:
      tags:
        - Blockchain
      summary: Get Transactions by Message
      description: Retrieves a list of transactions related to a specific message
      operationId: getTransactionsByMessage
      parameters:
        - name: direction
          in: query
          description: The direction of the message (in or out)
          required: true
          schema:
            type: string
            enum:
              - in
              - out
            default: out
        - name: msg_hash
          in: query
          description: The hash of the message
          required: true
          schema:
            type: string
            default: po4/F9OgHrJGTUCtobScZrW/gOwVPj7s3f40HV32EII=
        - name: limit
          in: query
          description: The maximum number of transactions to return
          required: false
          schema:
            type: integer
            default: 128
        - name: offset
          in: query
          description: The number of transactions 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:
                  transactions:
                    type: array
                    items:
                      type: object
                      properties:
                        hash:
                          type: string
                          description: The transaction hash
                        lt:
                          type: string
                          description: The logical time of the transaction
                        account:
                          type: string
                          description: The account address involved in the transaction
                        now:
                          type: integer
                          description: The timestamp of the transaction
                        origStatus:
                          type: string
                          description: The original status of the account
                        endStatus:
                          type: string
                          description: The end status of the account
                        totalFees:
                          type: string
                          description: The total fees for the transaction

````