> ## Documentation Index
> Fetch the complete documentation index at: https://sl-6d1f19fe-mintlify-ff95e355.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# List crypto currencies

> List all supported cryptocurrencies with live rates.



## OpenAPI

````yaml https://api.streamloop.app/v1/openapi.json get /crypto/currencies
openapi: 3.1.0
info:
  contact:
    name: Streamloop
    url: https://streamloop.app
  description: >-
    The Streamloop REST API. Authenticate with either an `X-API-Key` header (a
    Streamloop API key, prefix `sl_` — simplest for programmatic clients) or an
    OAuth 2.1 bearer access token (obtain one via https://auth.streamloop.app).
    Collections are cursor-paginated (`limit` + `cursor`, returning `{ data,
    page }`). Errors are RFC 7807 problem documents.
  summary: >-
    Programmatic access to Streamloop — create and control 24/7 loop streams,
    manage media, destinations, playlists, and billing.
  title: Streamloop API
  version: 1.0.0
servers:
  - description: Production
    url: https://api.streamloop.app/v1
security:
  - oauth2: []
  - bearerAuth: []
  - apiKey: []
tags:
  - description: The authenticated user's account.
    name: account
  - description: Credits, usage analytics, invoices, and top-ups.
    name: billing
  - description: Crypto deposit options for topping up credits.
    name: crypto
  - description: Manage streaming destinations (custom RTMP).
    name: destinations
  - description: 'Service metadata: status and the OpenAPI document (unauthenticated).'
    name: meta
  - description: Manage and publish stream playlists.
    name: playlists
  - description: Create, control, schedule, and monitor 24/7 loop streams.
    name: streams
  - description: Upload and manage source media (video/audio).
    name: uploads
paths:
  /crypto/currencies:
    get:
      tags:
        - crypto
      summary: List crypto currencies
      description: List all supported cryptocurrencies with live rates.
      operationId: listCryptoCurrencies
      responses:
        '200':
          content:
            application/json:
              schema:
                items:
                  $ref: '#/components/schemas/CryptoCurrency'
                type: array
          description: Successful response.
          headers:
            RateLimit-Limit:
              description: Requests allowed per window.
              schema:
                type: integer
            RateLimit-Remaining:
              description: Requests remaining in the current window.
              schema:
                type: integer
            RateLimit-Reset:
              description: Seconds until the window resets.
              schema:
                type: integer
        '401':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: Missing or invalid access token.
        '403':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: The token lacks the required scope or access to the resource.
        '404':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: The resource does not exist or is not visible to the caller.
        '422':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: The request body or parameters are invalid.
        '429':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: Rate limit exceeded. Retry after the indicated delay.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
        '502':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
          description: The upstream data service returned an error.
      security:
        - oauth2:
            - streamloop:read
        - bearerAuth: []
        - apiKey: []
components:
  schemas:
    CryptoCurrency:
      properties:
        chainId:
          description: >-
            EVM chain ID a WalletConnect/wagmi client should switch to before
            signing.

            Null for non-EVM chains (Solana, Tron, Bitcoin, TON, …) — those need

            their own connector libraries.
          type:
            - integer
            - 'null'
        contractAddress:
          description: >-
            Token contract address for ERC20-style tokens on EVM chains

            (and SPL mint for Solana). Null for native coins (ETH, SOL, MATIC,
            BTC, …)

            where a wallet sends a plain transfer instead of calling a contract.
          type:
            - string
            - 'null'
        decimals:
          description: >-
            Decimals for unit conversion. ERC20 tokens vary (USDT=6, DAI=18);
            native

            coins follow chain convention (ETH=18, SOL=9, BTC=8). Defaults to 18
            when

            unknown so EVM transfers stay safe.
          type: integer
        icon:
          description: SVG icon URL.
          type: string
        id:
          description: 0xProcessing currency identifier, e.g. "USDT (TRC20)" or "BTC".
          type: string
        name:
          description: Human-readable name from manifest, e.g. "Tether".
          type: string
        network:
          description: >-
            Network code from the manifest, e.g. "TRC20", "ERC20", "POLYGON",
            "SOL".
          type: string
        rateUSD:
          description: Price of 1 unit in USD (from Binance; 1.0 for stablecoins).
          type: number
        symbol:
          description: Base symbol, e.g. "USDT".
          type: string
        transferKind:
          description: How a frontend should construct the payment transaction.
          enum:
            - EVM_NATIVE
            - EVM_ERC20
            - NON_EVM
          type: string
      required:
        - decimals
        - icon
        - id
        - name
        - network
        - rateUSD
        - symbol
        - transferKind
      type: object
    Problem:
      description: RFC 7807 problem-details error body.
      properties:
        code:
          description: A stable, machine-readable error code.
          type: string
        detail:
          description: A human-readable explanation specific to this occurrence.
          type: string
        status:
          description: The HTTP status code.
          type: integer
        title:
          description: A short, human-readable summary of the problem.
          type: string
        type:
          description: A URI reference identifying the problem type.
          format: uri-reference
          type: string
      required:
        - type
        - title
        - status
        - detail
        - code
      type: object
  securitySchemes:
    oauth2:
      description: OAuth 2.1 authorization-code flow with PKCE.
      flows:
        authorizationCode:
          authorizationUrl: https://auth.streamloop.app/api/auth/oauth2/authorize
          scopes:
            streamloop:billing: Read billing/usage and create top-up links
            streamloop:destructive: Delete streams and destinations
            streamloop:read: Read streams, destinations, playlists, and billing status
            streamloop:write: Create and control streams, destinations, and playlists
          tokenUrl: https://auth.streamloop.app/api/auth/oauth2/token
      type: oauth2
    bearerAuth:
      bearerFormat: JWT
      description: An OAuth 2.1 bearer access token.
      scheme: bearer
      type: http
    apiKey:
      description: >-
        A Streamloop API key (prefix `sl_`), sent in the `X-API-Key` header.
        Create and manage keys in the dashboard. The simplest auth for
        programmatic / agent clients — no OAuth flow required; the key acts as
        its owning user.
      in: header
      name: X-API-Key
      type: apiKey

````