> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/invoices/listing-invoice-currencies-and-networks.md).

# Listing invoice currencies and networks

Two lookups return the currencies and networks available for invoices across the platform. Use them to build a currency and network selector in your own interface: the currencies lookup gives you the codes and symbols to display, the networks lookup gives you the network codes to send. Neither reflects your account's configuration — to see which combinations are enabled for you, use [Listing invoice currency pairs](https://docs.txn.io/invoices/listing-invoice-currency-pairs.md).

To build a selector:

1. Call [Listing invoice currencies](#listing-invoice-currencies) and offer the entries with `crypto: true` as payment options.
2. Call [Listing invoice networks](#listing-invoice-networks) and group the entries by `currencyCode`. Show `name` to the customer and pass `code` as the `network` parameter of [Create invoice](https://docs.txn.io/invoices/creating-invoice.md), together with the currency code as `chargedCurrency`.

Both lookups are paginated and return up to 50 entries per page by default.

## Listing invoice currencies

<mark style="color:green;">`GET`</mark> `/api/public/v1/invoices/currencies`

Returns the cryptocurrencies that have at least one network enabled for invoices, plus all fiat currencies. Fiat currencies are listed because an invoice can be denominated in them (`billedCurrency`); a customer cannot pay with them.

**Headers**

| Name          | Value                      |
| ------------- | -------------------------- |
| Content-Type  | `application/vnd.api+json` |
| Authorization | `Bearer <api_key>`         |

**URL Parameters**

| Name      | Type    | Description                                    |
| --------- | ------- | ---------------------------------------------- |
| page      | integer | Page number, starting from 1. Defaults to 1.   |
| per\_page | integer | Entries per page. Defaults to 50, maximum 100. |

**cURL**

```bash
curl "https://api.sandbox.txn.io/api/public/v1/invoices/currencies" \
     -H 'Content-Type: application/vnd.api+json' \
     -H 'Authorization: Bearer <api_key>'
```

**Response Body**

<table><thead><tr><th>Name</th><th width="97">Type</th><th>Description</th></tr></thead><tbody><tr><td>data[].id</td><td>string</td><td>Currency code. Same as <code>code</code>.</td></tr><tr><td>data[].type</td><td>string</td><td>Always <code>currencies</code>.</td></tr><tr><td>data[].attributes.code</td><td>string</td><td>Currency code.</td></tr><tr><td>data[].attributes.crypto</td><td>boolean</td><td><code>true</code> for cryptocurrencies, <code>false</code> for fiat.</td></tr><tr><td>data[].attributes.symbol</td><td>string</td><td>Display symbol for the currency.</td></tr><tr><td>data[].attributes.subunitToUnit</td><td>number</td><td>Number of smallest units in one whole unit (e.g. <code>100000000</code> for BTC, <code>100</code> for EUR).</td></tr><tr><td>data[].relationships.networks</td><td>object</td><td>Placeholder only; network objects are not included in this response. Use <a href="#listing-invoice-networks">the networks lookup</a> below.</td></tr><tr><td>meta.page</td><td>number</td><td>Current page.</td></tr><tr><td>meta.per_page</td><td>number</td><td>Entries per page.</td></tr><tr><td>meta.total</td><td>number</td><td>Total number of currencies.</td></tr></tbody></table>

**Response**

The sample is shortened to three entries.

{% tabs %}
{% tab title="HTTP 200" %}

```json
{
  "data": [
    {
      "id": "BTC",
      "type": "currencies",
      "attributes": {
        "code": "BTC",
        "crypto": true,
        "symbol": "฿",
        "subunitToUnit": 100000000
      },
      "relationships": {
        "networks": {
          "meta": {
            "included": false
          }
        }
      }
    },
    {
      "id": "USDT",
      "type": "currencies",
      "attributes": {
        "code": "USDT",
        "crypto": true,
        "symbol": "₮",
        "subunitToUnit": 1000000
      },
      "relationships": {
        "networks": {
          "meta": {
            "included": false
          }
        }
      }
    },
    {
      "id": "EUR",
      "type": "currencies",
      "attributes": {
        "code": "EUR",
        "crypto": false,
        "symbol": "€",
        "subunitToUnit": 100
      },
      "relationships": {
        "networks": {
          "meta": {
            "included": false
          }
        }
      }
    }
  ],
  "meta": {
    "page": 1,
    "per_page": 50,
    "total": 40
  },
  "jsonapi": {
    "version": "1.0"
  }
}
```

{% endtab %}
{% endtabs %}

## Listing invoice networks

<mark style="color:green;">`GET`</mark> `/api/public/v1/invoices/networks`

Returns the networks enabled for invoice payments. `currencyCode` tells you which currency each network carries, so a currency such as USDT appears once per network it is available on.

**Headers**

| Name          | Value                      |
| ------------- | -------------------------- |
| Content-Type  | `application/vnd.api+json` |
| Authorization | `Bearer <api_key>`         |

**URL Parameters**

| Name      | Type    | Description                                    |
| --------- | ------- | ---------------------------------------------- |
| page      | integer | Page number, starting from 1. Defaults to 1.   |
| per\_page | integer | Entries per page. Defaults to 50, maximum 100. |

**cURL**

```bash
curl "https://api.sandbox.txn.io/api/public/v1/invoices/networks" \
     -H 'Content-Type: application/vnd.api+json' \
     -H 'Authorization: Bearer <api_key>'
```

**Response Body**

<table><thead><tr><th>Name</th><th width="97">Type</th><th>Description</th></tr></thead><tbody><tr><td>data[].id</td><td>string</td><td>Network ID.</td></tr><tr><td>data[].type</td><td>string</td><td>Always <code>network</code>.</td></tr><tr><td>data[].attributes.code</td><td>string</td><td>Network code. Pass it as the <code>network</code> parameter in [Create invoice](creating-invoice.md).</td></tr><tr><td>data[].attributes.name</td><td>string</td><td>Human-readable network name, suitable for display.</td></tr><tr><td>data[].attributes.currencyCode</td><td>string</td><td>Code of the currency carried on this network.</td></tr><tr><td>meta.page</td><td>number</td><td>Current page.</td></tr><tr><td>meta.per_page</td><td>number</td><td>Entries per page.</td></tr><tr><td>meta.total</td><td>number</td><td>Total number of networks.</td></tr></tbody></table>

**Response**

The sample is shortened to three entries.

{% tabs %}
{% tab title="HTTP 200" %}

```json
{
  "data": [
    {
      "id": "8ededca3-a1cd-4b46-8c3a-14915f706ab2",
      "type": "network",
      "attributes": {
        "currencyCode": "USDT",
        "name": "Tron (TRC20)",
        "code": "ttrx:usdt"
      }
    },
    {
      "id": "c0369c57-da08-4c60-b5ee-63e1e43d5ae4",
      "type": "network",
      "attributes": {
        "currencyCode": "BTC",
        "name": "Bitcoin",
        "code": "tbtc"
      }
    },
    {
      "id": "e89a05d9-2528-4f28-ac70-dcde90f497aa",
      "type": "network",
      "attributes": {
        "currencyCode": "ETH",
        "name": "Ethereum",
        "code": "hteth"
      }
    }
  ],
  "meta": {
    "page": 1,
    "per_page": 50,
    "total": 19
  },
  "jsonapi": {
    "version": "1.0"
  }
}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Network codes in the Sandbox environment differ from those in Production — testnet networks are prefixed (`tbtc`, `ttrx:usdt`, `hteth`). Read the codes from the environment you are calling rather than hard-coding them. See [Supported currencies](https://docs.txn.io/api-basics/supported-currencies.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.txn.io/invoices/listing-invoice-currencies-and-networks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
