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

# getTokenData | TON v2

> The getTokenData method retrieves data about a specific token on the TON blockchain. Available on TON v2 via Chainstack JSON-RPC nodes.

The `getTokenData` method retrieves data about a specific token on the TON blockchain. This method is useful for obtaining detailed information about TON-based tokens, including their name, symbol, supply, and other characteristics.

<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

* `address` (string, required) — The address of the token contract. Example: `EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs`.

## JSON-RPC example

```shell Shell theme={"system"}
curl -X POST \
  'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2/jsonRPC' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "unpackAddress",
    "params": {
      "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
    }
  }'
```

## Response

* `name` (string) — The name of the token.
* `symbol` (string) — The symbol or ticker of the token.
* `decimals` (integer) — The number of decimal places for the token.
* `totalSupply` (string) — The total supply of the token.
* `mintable` (boolean) — Indicates whether new tokens can be minted.
* `burnable` (boolean) — Indicates whether tokens can be burned (destroyed).
* `address` (string) — The address of the token contract.

## Use case

A possible use case for the `getTokenData` method in TON is for applications that deal with TON-based tokens, such as:

1. Wallet applications displaying token information to users.
2. Decentralized exchanges (DEXs) fetching token data for listing and trading purposes.
3. Block explorers providing detailed token information.
4. DApps that need to interact with various tokens and require their metadata.


## OpenAPI

````yaml openapi/ton_node_api/v2/getTokenData.json GET /getTokenData
openapi: 3.0.0
info:
  title: getTokenData example
  version: 1.0.0
  description: >-
    This is an API example for getTokenData, a method to retrieve data about a
    specific token on the TON blockchain.
servers:
  - url: >-
      https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2
security: []
paths:
  /getTokenData:
    get:
      tags:
        - TON Operations
      summary: getTokenData
      operationId: getTokenData
      parameters:
        - name: address
          in: query
          required: true
          description: The address of the token contract
          schema:
            type: string
            default: EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs
          example: EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs
      responses:
        '200':
          description: Data about the specified token
          content:
            application/json:
              schema:
                type: object
                properties:
                  name:
                    type: string
                    description: The name of the token
                  symbol:
                    type: string
                    description: The symbol of the token
                  decimals:
                    type: integer
                    description: The number of decimal places for the token
                  totalSupply:
                    type: string
                    description: The total supply of the token
                  mintable:
                    type: boolean
                    description: Whether the token is mintable
                  burnable:
                    type: boolean
                    description: Whether the token is burnable
                  address:
                    type: string
                    description: The address of the token contract

````