> ## Documentation Index > Fetch the complete documentation index at: https://docs.cryptoprocessing.com/llms.txt > Use this file to discover all available pages before exploring further. # List supported currencies > Get a list of supported currencies in the environment, minimum deposit amounts, and deposit and withdrawal fees. The list of supported currencies in the sandbox environment is different from the list in the production environment. ## OpenAPI ````yaml POST /v2/currencies/list openapi: 3.0.0 info: title: Merchant Backend V2 version: '1.0' description: Documentation for merchant backend processing endpoints servers: - url: https://app.cryptoprocessing.com/api security: - xProcessingKey: [] tags: - name: Status - name: Balance - name: Currencies - name: Deposit addresses - name: Withdrawal - name: Exchange - name: Invoices - name: Transactions paths: /v2/currencies/list: post: tags: - Currencies summary: List supported currencies description: >- Get a list of supported currencies in the environment, minimum deposit amounts, and deposit and withdrawal fees. operationId: post-currencies-list parameters: - $ref: '#/components/parameters/XProcessingSignatureHeader' requestBody: required: false description: > Both an empty JSON object (`{}`) and a completely empty (zero-byte) body are accepted to list all [supported currencies](/supported-currencies). `Content-Type: application/json` is still required if you send `{}` — but if the body is truly empty (zero bytes), `Content-Type` isn't checked at all (it can be omitted or set to any value). Include `visible` to filter by [Balances tab](/portal#viewing-your-balances) visibility. content: application/json: schema: type: object properties: visible: type: boolean description: > Filters currencies by their visibility on the [Balances tab](/portal#viewing-your-balances) of the portal. - `true` returns currencies that are enabled for the merchant account and visible on the Balances tab. - `false` returns currencies that are enabled for the merchant account but hidden from the Balances tab. There's no single request that returns all currencies enabled for the merchant account directly — combine the results of a `true` call and a `false` call to get that full list. If omitted, all [supported currencies](/supported-currencies) are returned, regardless of whether they are enabled or disabled, or visible or hidden on the [Balances tab](/portal#viewing-your-balances). examples: Basic example: value: {} responses: '200': description: OK content: application/json: schema: type: object required: - data properties: data: type: array items: type: object required: - id - type - currency - minimum_amount - minimum_withdrawal_amount - deposit_fee_percent - withdrawal_fee_percent - precision properties: id: type: integer description: Currency ID. type: type: string description: Currency type (crypto or fiat). enum: - crypto - fiat currency: type: string description: Currency code. minimum_amount: type: string description: The minimum deposit amount for this currency. minimum_withdrawal_amount: type: string description: The minimum withdrawal amount for this currency. deposit_confirmations: type: integer description: > The number of confirmations required before a deposit is credited. Omitted for fiat currencies. For some cryptocurrencies, smaller amount deposits may require less confirmations than returned by the API before the funds are credited. See [Confirmations and limits](/confirmations-and-limits) for the number of confirmations required in such cases. deposit_fee_percent: type: string description: >- The fee that is charged for deposits in this currency, in percentage of the deposit amount. withdrawal_fee_percent: type: string description: >- The fee that is charged for withdrawals in this currency, in percentage of the withdrawal amount. precision: type: integer description: The number of decimal places. examples: Basic example: value: data: - id: 1 type: crypto currency: BTC minimum_amount: '0.00010000' minimum_withdrawal_amount: '0.00020000' deposit_confirmations: 1 deposit_fee_percent: '0.000700' withdrawal_fee_percent: '0.010000' precision: 8 - id: 5 type: crypto currency: ETH minimum_amount: '0.00200000' minimum_withdrawal_amount: '0.00200000' deposit_confirmations: 10 deposit_fee_percent: '0.010000' withdrawal_fee_percent: '0.000000' precision: 8 - id: 87 type: crypto currency: USDC minimum_amount: '5.00000000' minimum_withdrawal_amount: '5.00000000' deposit_confirmations: 10 deposit_fee_percent: '0.010000' withdrawal_fee_percent: '0.000000' precision: 8 '400': description: Bad Request. content: application/json: schema: $ref: '#/components/schemas/ValidationOrMalformedJson' examples: Invalid visible: value: errors: visible: The visible field must be true or false. Malformed JSON: summary: Invalid JSON body value: error: Bad content format code: bad_content_format '403': $ref: '#/components/responses/HeaderAuthorization' components: parameters: XProcessingSignatureHeader: name: X-Processing-Signature in: header required: true description: >- Hex-encoded HMAC-SHA512 signature of the request body, [generated using your secret key](/api-reference/authentication). schema: type: string schemas: ValidationOrMalformedJson: oneOf: - type: object title: ValidationError description: One or more request parameters failed validation. properties: errors: type: object description: > A map of request field names to a human-readable validation error message for that field. The exact set of possible keys and messages is endpoint-specific — see [API errors](/api-reference/errors#400-bad-request) for the full reference. additionalProperties: type: string description: Human-readable validation error message for this field. - type: object title: MalformedJson description: >- The request body is not valid JSON or the Content-Type header is not set to `application/json`. properties: error: type: string code: type: string responses: HeaderAuthorization: description: | Forbidden content: application/json: schema: type: object properties: error: type: string description: Human-readable error message. code: type: string description: Error code. description: >- Invalid or missing headers, or the API key does not have access to the endpoint. Refer to [Errors](/api-reference/errors#403-forbidden) for troubleshooting steps. examples: Bad signature header: value: error: Bad signature header code: bad_header_signature API key does not have the required ability: value: error: The API key does not have access to this endpoint. code: api_key_ability_required No signature header: value: error: No signature header code: required_header_signature Bad key header: value: error: Bad key header code: bad_header_key No key header: value: error: No key header code: required_header_key securitySchemes: xProcessingKey: type: apiKey description: Your [API key](/merchant-administration/generate-and-activate-api-keys). in: header name: X-Processing-Key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.