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

# Get CLMM dynamic-fee configurations

> Retrieve the calibrated `DynamicFeeConfig` tiers a new CLMM pool can opt into when
`enableDynamicFee=true` is passed to `CreateCustomizablePool`. Each entry exposes the
per-tier parameters (filter period, decay period, reduction factor, dynamic-fee
control, max volatility accumulator) that govern the volatility-tracking surcharge.
Cached 60 seconds.




## OpenAPI

````yaml /api-reference/openapi/api-v3.yaml get /main/clmm-dynamic-config
openapi: 3.0.3
info:
  title: Raydium API v3
  version: 3.0.0
  description: >-
    The Raydium API v3 provides REST endpoints for querying liquidity pools,
    mint information, farm details, IDO pools, and chain metadata for the Solana
    blockchain. Used by wallets, aggregators, and traders to source price feeds,
    pool data, and routing information.
servers:
  - url: https://api-v3.raydium.io
    description: Production (Mainnet)
  - url: https://api-v3-devnet.raydium.io
    description: Development (Devnet)
security: []
tags:
  - name: Main
    description: Core API endpoints for chain info, TVL, and configuration
  - name: Mint
    description: Token mint information and pricing
  - name: Pools
    description: Liquidity pool info, keys, and historical data
  - name: Farms
    description: Farm pool information and keys
  - name: IDO
    description: IDO pool information and keys
paths:
  /main/clmm-dynamic-config:
    get:
      tags:
        - Main
      summary: Get CLMM dynamic-fee configurations
      description: >
        Retrieve the calibrated `DynamicFeeConfig` tiers a new CLMM pool can opt
        into when

        `enableDynamicFee=true` is passed to `CreateCustomizablePool`. Each
        entry exposes the

        per-tier parameters (filter period, decay period, reduction factor,
        dynamic-fee

        control, max volatility accumulator) that govern the volatility-tracking
        surcharge.

        Cached 60 seconds.
      operationId: getMainClmmDynamicConfig
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/ApiResponse'
                  - type: object
                    properties:
                      data:
                        type: array
                        items:
                          type: object
                          properties:
                            id:
                              type: string
                              description: DynamicFeeConfig PDA
                            index:
                              type: integer
                            filterPeriod:
                              type: integer
                              description: >-
                                Seconds; volatility decays toward zero after
                                this window
                            decayPeriod:
                              type: integer
                              description: Seconds; full half-life of accumulator decay
                            reductionFactor:
                              type: integer
                              description: Per-step decay numerator (denominator = 10000)
                            maxFeeRateNumerator:
                              type: integer
                              description: >-
                                Cap on dynamic-fee surcharge (denominator =
                                1_000_000)
                            dynamicFeeControl:
                              type: integer
                              description: >-
                                Tick-distance scaling numerator (denominator =
                                100_000)
components:
  schemas:
    ApiResponse:
      type: object
      description: >-
        Common response envelope. The `data` field is supplied by each
        endpoint's response schema via `allOf` and is therefore not declared on
        the base envelope.
      required:
        - id
        - success
      properties:
        id:
          type: string
          description: Request ID (UUID)
        success:
          type: boolean
          description: Whether the request was successful
        msg:
          type: string
          description: Error message if success is false

````