> 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.md).

# Public Endpoints

Public endpoints return data without authentication.

### Gateway

Unlike the Private API, the Public API routes through a single gateway. Each path prefix maps to the same host:

There is no single gateway. Each path prefix maps to its own service:

| Path prefix       | Host                                      |
| ----------------- | ----------------------------------------- |
| `/api/coins`      | `https://wallet-mutator-view.outpoll.com` |
| `/api/events/*`   | `https://event-service.outpoll.com`       |
| `/api/categories` | `https://event-service.outpoll.com`       |
| `/api/tags/*`     | `https://event-service.outpoll.com`       |

Use HTTPS for every request.

This host serves every public REST endpoint in this section.

### Authentication

No authentication required.

### Sections

* [Public API Overview](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/public-api-overview.md) for the shared quickstart, errors, and pagination rules.
* [Search Events](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/search-events.md) for market discovery and filtering.
* [Get Available Coins](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-available-coins.md) for supported assets and collateral metadata.
* [Get Categories](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-categories.md) for category filters and navigation.
* [Get Popular Tags](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-popular-tags.md) for trending discovery tags.

### Example requests

Use the gateway directly for both `GET` and `POST` endpoints.

#### Search events

```bash
curl -X POST "https://outpoll.com/api/events/search?page=0&size=20" \
  -H "Content-Type: application/json" \
  --data '{"sb":"VOLUME_24H","sd":"DESC","l":"en","ss":"bitcoin"}'
```

### Endpoints

* [Get Available Coins](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-available-coins.md) — `GET /api/coins`
* [Search Events](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/search-events.md) — `POST /api/events/search`
* [Get Categories](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-categories.md) — `GET /api/categories`
* [Get Popular Tags](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/get-popular-tags.md) — `GET /api/tags/popular`

### Pagination

Only [Search Events](https://docs.outpoll.com/api/prediction-api/rest-api/public-endpoints/search-events.md) is paginated.

Use these query parameters:

* `page` — zero-based page number
* `size` — items per page

Typical paginated responses include:

* `content` — current page items
* `totalElements` — total matching items
* `totalPages` — total page count

### Example IDs

* `evt_btc_100k_2026` for an event
* `mkt_btc_100k_yes_no` for a market
* `asset_btc_100k_yes` and `asset_btc_100k_no` for outcome assets
* `asset_usdc` for the quote asset


---

# 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.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.
