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

# multisig/orders | TON v3

> The multisig/orders endpoint retrieves pending and executed orders for multisig wallets. multisig/orders on TON v3 via Chainstack.

# Multisig Orders

The `multisig/orders` endpoint retrieves pending and executed orders for multisig wallets. Orders represent proposed transactions that require multiple signatures before execution.

<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

* `multisig_address` (string, optional) — Filter by multisig wallet address.
* `order_address` (string, optional) — Filter by specific order contract address.
* `is_executed` (boolean, optional) — Filter by execution status.
* `limit` (integer, optional) — Maximum number of orders to return. Default: `10`.
* `offset` (integer, optional) — Number of orders to skip for pagination. Default: `0`.

## Response

* `multisig_orders` (array) — Array of order objects:
  * `address` (string) — Order contract address.
  * `multisig_address` (string) — Parent multisig wallet address.
  * `order_seqno` (integer) — Order sequence number.
  * `threshold` (integer) — Required number of signatures.
  * `signers_num` (integer) — Total number of possible signers.
  * `approvals_num` (integer) — Current number of approvals.
  * `approvals` (array) — List of addresses that have approved.
  * `expiration_date` (integer) — Order expiration timestamp.
  * `is_executed` (boolean) — Whether the order has been executed.

* `address_book` (object) — Address book mapping.

## Use case

The `multisig/orders` endpoint is crucial for multisig transaction management:

1. Signer interfaces showing orders awaiting their approval.
2. Treasury dashboards displaying pending transactions.
3. Alert systems notifying when orders need signatures.
4. Audit tools tracking multisig transaction history.
5. Governance tools managing DAO proposals and executions.

Here's an example of getting pending orders for a multisig wallet:

<CodeGroup>
  ```shell shell theme={"system"}
  curl -X GET \
    'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/multisig/orders?is_executed=false&limit=5' \
    -H 'accept: application/json'
  ```
</CodeGroup>

<Tip>
  Monitor `expiration_date` to ensure orders are signed before they expire. Orders that expire without enough signatures will need to be recreated.
</Tip>


## OpenAPI

````yaml openapi/ton_node_api/v3/getMultisigOrders.json GET /multisig/orders
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:
  /multisig/orders:
    get:
      tags:
        - Multisig
      summary: Get Multisig Orders
      description: Get pending orders for multisig wallets
      operationId: getMultisigOrders
      parameters:
        - name: multisig_address
          in: query
          description: Filter by multisig wallet address
          schema:
            type: string
        - name: order_address
          in: query
          description: Filter by order contract address
          schema:
            type: string
        - name: is_executed
          in: query
          description: Filter by execution status
          schema:
            type: boolean
        - name: limit
          in: query
          description: Maximum number of orders to return
          schema:
            type: integer
            default: 10
        - name: offset
          in: query
          description: Number of orders to skip
          schema:
            type: integer
            default: 0
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  multisig_orders:
                    type: array
                    items:
                      type: object
                      properties:
                        address:
                          type: string
                          description: Order contract address
                        multisig_address:
                          type: string
                          description: Parent multisig wallet address
                        order_seqno:
                          type: integer
                          description: Order sequence number
                        threshold:
                          type: integer
                          description: Required signatures
                        signers_num:
                          type: integer
                          description: Total number of signers
                        approvals_num:
                          type: integer
                          description: Current approvals count
                        approvals:
                          type: array
                          items:
                            type: string
                          description: List of approving addresses
                        expiration_date:
                          type: integer
                          description: Order expiration timestamp
                        is_executed:
                          type: boolean
                          description: Whether order is executed
                  address_book:
                    type: object
                    description: Address book mapping

````