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

# Fee configuration

> The fee schedule applied to your routes. Send your publishable key to see YOUR negotiated rate; without a key you get the public default.

Use this to display fees in your UI rather than hard-coding them — rates can change per partner without an API version bump.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/fee-config
openapi: 3.1.0
info:
  title: Hypermid API
  description: >-
    Price and execute cross-chain swaps, read reference data and payer balances,
    and quote the fiat on-ramp. Quotes return an executable `transactionRequest`
    your frontend submits directly, so Hypermid never custodies the funds.


    Payments — `checkout`, `deposit`, and `withdrawal` sessions — and
    payment-link management are available through these merchant REST endpoints
    and the [`@hypermid/sdk`](https://docs.hypermid.io/sdk/payments) package.
    Payer-facing routes are intentionally omitted.
  version: 0.2.0
  contact: {}
servers:
  - url: https://server.hypermid.io
    description: Production — live keys (sk_live_…)
  - url: https://server.hypermid.io
    description: Sandbox — test keys (sk_test_…), testnets only
security: []
tags:
  - name: payments
    description: >-
      Create and read payment sessions, manage webhooks, and configure payout
      addresses with a secret partner key.
  - name: payment links
    description: >-
      Create, read, version, and revoke reusable checkout payment links with a
      secret partner key.
  - name: quote
    description: >-
      Route pricing for the orchestration product. Returns an executable
      `transactionRequest` your frontend submits directly, so Hypermid never
      custodies the funds.
  - name: status
    description: >-
      Resolve the state of a submitted swap or transfer. Two endpoints with
      different audiences — see each one's description before choosing.
  - name: catalog
    description: >-
      Reference data an integration needs to render a picker: supported chains
      and tokens, prices, routable connections, and fee configuration. A sandbox
      key sees only testnets here.
  - name: balances
    description: Read a payer wallet's token balances across supported chains.
  - name: onramp
    description: >-
      The fiat rail — card and bank payment for crypto, quoted and settled
      through our onramp partner. Requires per-partner onramp credentials on
      your account.
  - name: webhooks
    description: >-
      Events Hypermid sends TO you when a session completes. These are requests
      we make to your server, not endpoints you call.
paths:
  /v1/fee-config:
    get:
      tags:
        - catalog
      summary: Fee configuration
      description: >-
        The fee schedule applied to your routes. Send your publishable key to
        see YOUR negotiated rate; without a key you get the public default.


        Use this to display fees in your UI rather than hard-coding them — rates
        can change per partner without an API version bump.
      operationId: FeeConfigController_feeConfig
      parameters:
        - name: x-api-key
          required: true
          in: header
          schema:
            type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FeeConfigDto'
      security:
        - x-api-key: []
components:
  schemas:
    FeeConfigDto:
      type: object
      properties:
        integrator:
          type: string
          example: hypermid
          description: >-
            Integrator identity the fee is resolved for — your partner slug, or
            the public default.
        fee:
          type: number
          description: Fee as a fraction (feeBps/10000).
          example: 0.003
        feeBps:
          type: number
          example: 30
          description: >-
            Fee in basis points (100 bps = 1%). The same value as `fee`,
            expressed as an integer.
        partner:
          type: string
          description: Partner name when resolved via X-API-Key.
      required:
        - integrator
        - fee
        - feeBps
  securitySchemes:
    x-api-key:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Soft-auth read routes accept `x-api-key` with a publishable or partner
        key; money-moving routes require a secret partner key in `Authorization:
        Bearer`.

````