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

# Get Supported Networks and Limits (v1)

> Get Supported Networks and Limits

---

**Field notes (recovered from legacy docs)**

**Get Supported Networks and Limits**

**Response field values**

| Field | Possible Values |
| --- | --- |
| `transaction_type` (query) | `WITHDRAW`, `DEPOSIT` |
| `coins` (query) | Comma-separated symbols, e.g. `USDT`, `USDT,BTC` |
| `network_list[]` fields | Varies by network; may include `network_fee`, `depositMin`, `minAccuracy`, `address_regex`, `memo_regex`, `processing_time` |



## OpenAPI

````yaml /openapi-v1.json get /api/v1/wallet/coin/info
openapi: 3.1.0
info:
  title: Saber Money API (v1)
  version: v1
  description: >-
    ## Authentication


    There is no standalone API-key auth — every request must be **signed**. An
    API key by itself authenticates nothing. Each call requires four headers
    together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey +
    timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required —
    keyed with your API secret), `X-Timestamp` (unix seconds), and
    `X-Request-Id` (any unique string per request). The signature must be
    computed by a client script; there is no way to derive it by hand. Use the
    HMAC Generator flow to compute valid values for manual testing.


    ## Common Authentication Errors


    - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id
    invalid","success":false}

    - **Invalid Secret**: {"error_code":6090,"message":"invalid
    secret","success":false}

    - **Timestamp (Older than 10 secs)**:
    {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false}
servers:
  - url: https://api.saber.money
security: []
paths:
  /api/v1/wallet/coin/info:
    get:
      tags:
        - Wallet Operations
      summary: Get Supported Networks and Limits (v1)
      description: >-
        Get Supported Networks and Limits


        ---


        **Field notes (recovered from legacy docs)**


        **Get Supported Networks and Limits**


        **Response field values**


        | Field | Possible Values |

        | --- | --- |

        | `transaction_type` (query) | `WITHDRAW`, `DEPOSIT` |

        | `coins` (query) | Comma-separated symbols, e.g. `USDT`, `USDT,BTC` |

        | `network_list[]` fields | Varies by network; may include
        `network_fee`, `depositMin`, `minAccuracy`, `address_regex`,
        `memo_regex`, `processing_time` |
      operationId: get-supported-networks-and-limits-v1
      parameters:
        - name: coins
          in: query
          required: true
          description: The coins parameter
          schema:
            type: string
            description: The coins parameter
        - name: X-Api-Key
          in: header
          required: true
          description: Your API key (configured in credentials)
          schema:
            type: string
        - name: X-Signature
          in: header
          required: true
          description: >-
            HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256
            of `apiKey + timestamp` (or `apiKey + timestamp + userId` when
            X-User-Id is required), keyed with your API secret. The HMAC
            Generator flow computes this for you.
          schema:
            type: string
        - name: X-Timestamp
          in: header
          required: true
          description: >-
            Unix timestamp in seconds (auto-generated) Unix seconds, e.g.
            `Math.floor(Date.now() / 1000)`. Must match the timestamp used in
            the X-Signature computation.
          schema:
            type: string
        - name: X-Request-Id
          in: header
          required: true
          description: >-
            Unique request identifier (auto-generated) Any unique string per
            request, e.g. a UUID.
          schema:
            type: string
        - name: X-User-Id
          in: header
          required: true
          description: User UUID (set above)
          schema:
            type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        name:
                          type: string
                        symbol:
                          type: string
                        network_list:
                          type: array
                          items:
                            type: object
              example:
                success: true
                data:
                  - name: TetherUS
                    symbol: USDT
                    network_list:
                      - network: BSC
                        name: BNB Smart Chain (BEP20)
                        address_regex: ^(0x)[0-9A-Fa-f]{40}$
                        memo_regex: ''
                        processing_time: Typically takes 15 mins
                      - network: TRX
                        name: Tron (TRC20)
                        address_regex: ^T[1-9A-HJ-NP-Za-km-z]{33}$
                        memo_regex: ''
                        processing_time: Typically takes 5 mins

````

## Related topics

- [Get User Limits (v1)](/api-reference/limits/get-user-limits-v1.md)
- [Get Wallet Address (v1)](/api-reference/wallet-operations/get-wallet-address-v1.md)
- [Supported Configurations](/docs/supported-onramp-methods.md)
- [Get Buy Quote (v1)](/api-reference/onramp/get-buy-quote-v1.md)
- [Overview](/client/pool-account/overview.md)