> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plurex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> The Plurex Platform API uses a Command & Query Separation (CQS) architecture for managing exchange accounts, hosts, and venues.

The Plurex Platform API is designed to expose the full range of functionality available through the [Plurex web application](https://platform.plurex.io).

## CQS Architecture

The API follows a **Command & Query Separation (CQS)** pattern:

* **Queries**: Read-only operations used to fetch state. (e.g., listing venues, getting balances)
* **Commands**: State-changing operations used to perform actions. (e.g., submitting orders, creating accounts)

All operations use **HTTP POST** with JSON payloads, regardless of whether they are commands or queries.

## Key Modules

The Platform API is structured around several key functional areas:

<CardGroup cols={2}>
  <Card title="Venues" icon="building-columns" href="/api-reference/platform/venues/list">
    Explore available liquidity venues and their markets.
  </Card>

  <Card title="Hosts" icon="server" href="/api-reference/platform/hosts/list">
    Manage execution hosts (brokers), query wallets, positions, and orders.
  </Card>

  <Card title="Accounts" icon="user-gear" href="/api-reference/platform/accounts/list">
    Programmatically manage your linked exchange accounts.
  </Card>

  <Card title="Paper Trading" icon="flask" href="/api-reference/platform/paper/create">
    Create and manage paper trading accounts for testing.
  </Card>
</CardGroup>

## Authentication

All requests require authentication using your API Key and API Secret, which can be managed in your Plurex account settings.