> For the complete documentation index, see [llms.txt](https://docs.outpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-available-coins.md).

# Get Available Coins

Return the list of supported coins and assets

`GET`

### Overview

Returns the list of all supported coins and assets on the platform.

### Authentication

No authentication required.

### Request

* Method: `GET`
* Path: `/api/coins`
* Query parameters: None

### Response `200 OK`

```json
[
  {
    "i": "078dcd98-928d-479f-8110-ff6d27e44de2",
    "n": "USD Coin",
    "sn": "USDC",
    "ur": 1.0,
    "urd": "2026-01-15T10:30:00.000Z",
    "dpf": 6,
    "dps": 3,
    "ac": "ACTIVE",
    "iu": "https://example.com/usdc.png",
    "sc": false,
    "pmc": true
  }
]
```

| Field | Type    | Description                               |
| ----- | ------- | ----------------------------------------- |
| i     | string  | Coin ID                                   |
| n     | string  | Full coin name                            |
| sn    | string  | Short name or ticker                      |
| ur    | number  | USD exchange rate                         |
| urd   | string  | Rate update time in ISO 8601 format       |
| dpf   | integer | Decimal places for full precision         |
| dps   | integer | Decimal places for short display          |
| ac    | string  | Coin status                               |
| iu    | string  | Icon URL                                  |
| sc    | boolean | System coin flag                          |
| pmc   | boolean | Available as prediction market collateral |

### Error variants

Common public endpoint errors:

| Code | Description                         |
| ---- | ----------------------------------- |
| 400  | Bad Request — Invalid parameters    |
| 404  | Not Found — Resource does not exist |
| 500  | Internal Server Error               |

**Error response**

```json
{
  "status": 400,
  "error": "Bad Request",
  "message": "Invalid parameters"
}
```

### Python example

Install the dependency first.

```bash
pip install requests
```

Send the request and iterate over the result.

{% code title="get\_coins.py" %}

```python
import requests

BASE_URL = "https://wallet-mutator-view.outpoll.com"

response = requests.get(
    f"{BASE_URL}/api/coins",
    timeout=10,
)
response.raise_for_status()

coins = response.json()

for coin in coins:
    print(f"{coin['sn']:<6} {coin['n']:<20} rate={coin['ur']}")
```

{% endcode %}

Example output:

```
USDC   USD Coin             rate=1.0
```

{% hint style="info" %}
Use `response.raise_for_status()` to fail fast on HTTP errors.
{% 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.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-available-coins.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.
