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

# Token supply and decimals



## OpenAPI

````yaml openapi-spec/history.yaml get /api/sol/tokens/supply/{tokenMint}
openapi: 3.0.3
info:
  title: Raze Database API
  description: >
    Paid subscription API for Solana transaction data and history.


    Also hosts write utilities (`/utils/sol/*`): token launch, transfer, burn,

    consolidate, fees claim/config, and agent initialize — previously on

    `router.raze.bot`. Mixer/distribute removed 2026-07-25.


    ## Batch Requests

    All endpoints with path parameters (mint, signer, address, tokenMint,
    ownerAddress) support batch queries

    via comma-separated values. For example:
    `/api/sol/trades/mint/mint1,mint2,mint3?limit=50`


    - Maximum 10 values per batch request

    - Each value must be a valid address (>= 32 characters)

    - Single values behave identically to non-batch requests

    - Batch response format: `{ "success": true, "results": { "value1": {...},
    "value2": {...} }, "count": N, "timestamp": "..." }`

    - Each key in `results` contains the full single-entity response

    - Queries run in parallel for maximum performance
  version: 1.0.0
servers:
  - url: https://api.raze.bot
    description: >-
      Raze global History API — GeoDNS routes to the nearest region
      automatically
security:
  - ApiKeyAuth: []
paths:
  /api/sol/tokens/supply/{tokenMint}:
    get:
      summary: Token supply and decimals
      operationId: getTokenSupply
      parameters:
        - name: tokenMint
          in: path
          required: true
          schema:
            type: string
          example: Fyx78ew4wRY26gPj5CkTyuZ4kvW7CkPff5Jm2vNspump
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SupplyResponse'
        '400':
          description: Invalid token mint
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Server error or RPC not configured
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    SupplyResponse:
      type: object
      description: >
        Token supply and decimals. The endpoint tries multiple RPCs; if all
        return

        empty it falls back to a default (`supply: 1000000000`, `decimals: 6`)
        and

        sets `fallback: true`. On error, a `{ success: false, tokenMint, error
        }`

        shape is returned instead.
      properties:
        success:
          type: boolean
        tokenMint:
          type: string
        supply:
          type: number
          description: >
            UI supply. A NUMBER (can be fractional), not an integer.
            `1000000000` when the fallback default is used.
        decimals:
          type: integer
          nullable: true
        fallback:
          type: boolean
          description: >-
            True when the default supply/decimals were used because every RPC
            returned empty.
        error:
          type: string
          description: 'Present only on failure responses (success: false).'
        timestamp:
          type: string
          format: date-time
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
        code:
          type: string
        success:
          type: boolean
      example:
        error: Unauthorized
        message: Invalid API key
        code: INVALID_KEY
        success: false
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: apiKey

````