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

# List Venues

List the startup state of each configured Market Hub venue. This method does not return symbols; use [`MarketHub.ListSymbols`](/k4k3ru-docs/api/market-hub/list-symbols.md) for symbol discovery.

## Endpoint

| Property       | Value                     |
| -------------- | ------------------------- |
| URL            | `https://api.k4k3ru.com/` |
| HTTP method    | `POST`                    |
| RPC method     | `MarketHub.ListVenues`    |
| Authentication | Not required              |

## Request

### Request Body

This method uses the common [JSON-RPC request envelope](/k4k3ru-docs/api/json-rpc.md#request-envelope). Set `method` to `MarketHub.ListVenues`. The `params` field is optional.

When `params` is omitted or `null`, or when an empty object is provided, the method returns every venue enabled in the Market Hub configuration. Filters and pagination are not supported.

### Example Request

```bash
curl --request POST 'https://api.k4k3ru.com/' \
  --header 'Content-Type: application/json' \
  --data '{
    "id": "list-venues-1",
    "method": "MarketHub.ListVenues"
  }'
```

## Response

### Response Body

Successful requests use the common [JSON-RPC success response envelope](/k4k3ru-docs/api/json-rpc.md#success-response-envelope). Failed requests use the common [JSON-RPC error response envelope](/k4k3ru-docs/api/json-rpc.md#error-response-envelope).

The response includes only venues enabled in the Market Hub configuration. Venues are ordered by name in ascending lexical order.

### Result Fields

| Field                | Type   | Description                                                                |
| -------------------- | ------ | -------------------------------------------------------------------------- |
| `venues`             | array  | Configured venue states, ordered by venue name in ascending lexical order. |
| `venues[].name`      | string | Market-data venue.                                                         |
| `venues[].status`    | string | Startup state. Supported values are `starting`, `active`, and `failed`.    |
| `venues[].updatedAt` | string | Most recent state transition time in UTC RFC 3339 format.                  |

`starting` means that the venue client has not completed startup. `active` means that startup completed successfully, but does not guarantee continuous WebSocket connectivity or ongoing market-data delivery. `failed` means that the venue client failed during startup. Failure details are available in Market Hub application logs and are not exposed by this method.

### Errors

| Code              | When it occurs                                               |
| ----------------- | ------------------------------------------------------------ |
| `invalid_request` | The parameters are not an empty object or cannot be decoded. |

### Example Success Response

```json
{
  "id": "list-venues-1",
  "result": {
    "venues": [
      {
        "name": "binance",
        "status": "active",
        "updatedAt": "2026-08-17T08:46:16Z"
      },
      {
        "name": "btse",
        "status": "failed",
        "updatedAt": "2026-08-17T08:46:19Z"
      },
      {
        "name": "coinbase",
        "status": "active",
        "updatedAt": "2026-08-17T08:46:20Z"
      }
    ]
  }
}
```

The venue states and transition times shown above are examples. Use the values returned by the API.

### Example Error Response

```json
{
  "id": "list-venues-1",
  "error": {
    "code": "invalid_request"
  }
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://k4k3ru.gitbook.io/k4k3ru-docs/api/market-hub/list-venues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.