> For the complete documentation index, see [llms.txt](https://noodles-finance.gitbook.io/docs.noodles.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://noodles-finance.gitbook.io/docs.noodles.fi/coin/coin-info-list.md).

# Coin Info List

## Overview

The Coin Info List API provides a paginated list of coins with their basic information including metadata, pricing, and volume data. This endpoint supports filtering by specific coin identifiers and verification status.

## Endpoint

```
GET /api/v1/partner/coin-info-list
```

## Parameters

| Parameter  | Type    | Required | Description                                                                                                    |
| ---------- | ------- | -------- | -------------------------------------------------------------------------------------------------------------- |
| `coin`     | String  | No       | The coin identifier to filter by. If provided, only returns information for this specific coin.                |
| `verified` | Boolean | No       | Filter only verified coins. If true, only returns verified coins. If false or not provided, returns all coins. |
| `limit`    | Integer | No       | Number of coins to return per page. Default and maximum limits is 40 per page.                                 |
| `offset`   | Integer | No       | Number of coins to skip for pagination.                                                                        |

## Headers

| Header      | Required | Description                 |
| ----------- | -------- | --------------------------- |
| `x-api-key` | No       | API key for authentication. |

## Request Example

```sh
curl --location 'https://api.noodles.fi/api/v1/partner/coin-info-list?limit=2&offset=0' \
--header 'Accept-Encoding: application/json' \
--header 'x-api-key: YOUR_API_KEY'
```

## Request Example with Specific Coin

```sh
curl --location 'https://api.noodles.fi/api/v1/partner/coin-info-list?coin=0xdeeb7a4662eec9f2f3def03fb937a663dddaa2e215b8078a284d026b7946c270%3A%3Adeep%3A%3ADEEP' \
--header 'x-api-key: YOUR_API_KEY'
```

## Response Format

```json
{
    "code": 200,
    "message": "OK",
    "data": [
        {
            "coin_ident": "0x0000000000000000000000000000000000000000000000000000000000000002::sui::SUI",
            "name": "Sui",
            "symbol": "SUI",
            "icon_url": "https://imagedelivery.net/cBNDGgkrsEA-b_ixIp9SkQ/sui-coin.svg/public",
            "decimals": 9,
            "verified": true,
            "volume_24h": 289527019.66787374,
            "volume_change_24h": 0,
            "price": 3.9975,
            "price_change_1d": -0.67,
            "published_at": "2023-05-03T00:00:00.688Z"
        },
        {
            "coin_ident": "0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC",
            "name": "USDC",
            "symbol": "USDC",
            "icon_url": "https://imagedelivery.net/cBNDGgkrsEA-b_ixIp9SkQ/usdc.png/public",
            "decimals": 6,
            "verified": true,
            "volume_24h": 281317497.0878987,
            "volume_change_24h": -11.06,
            "price": 0.999723,
            "price_change_1d": -0.05,
            "published_at": "2024-09-09T17:09:30.583Z"
        }
    ],
    "pagination": {
        "offset": 0,
        "limit": 2
    }
}
```

## Response Fields

| Field        | Type     | Description                         |
| ------------ | -------- | ----------------------------------- |
| `code`       | `number` | HTTP status code (200 for success). |
| `message`    | `string` | Status message.                     |
| `data`       | `array`  | Array of coin information objects.  |
| `pagination` | `object` | Pagination information.             |

#### Coin Information Object

| Field               | Type      | Description                                      |
| ------------------- | --------- | ------------------------------------------------ |
| `coin_ident`        | `string`  | Unique coin identifier.                          |
| `name`              | `string`  | Full name of the coin.                           |
| `symbol`            | `string`  | Coin symbol/ticker.                              |
| `icon_url`          | `string`  | URL to the coin's icon image.                    |
| `decimals`          | `number`  | Number of decimal places for the coin.           |
| `verified`          | `boolean` | Whether the coin is verified.                    |
| `volume_24h`        | `number`  | 24-hour trading volume (may be null).            |
| `volume_change_24h` | `number`  | 24-hour volume change percentage (may be null).  |
| `price`             | `number`  | Current price of the coin (may be null).         |
| `price_change_1d`   | `number`  | 24-hour price change percentage (may be null).   |
| `published_at`      | `string`  | ISO timestamp when the coin was first published. |

***

> **See also:** [Environment Setup](/docs.noodles.fi/environment-setup/environment.md)


---

# 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://noodles-finance.gitbook.io/docs.noodles.fi/coin/coin-info-list.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.