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

# API reference overview

> Find the endpoints for market data, trading, Connect and your venue, and choose the key each request needs.

Use the API reference when you need an endpoint's request, response or errors. If you're making
your first request, start with [Choose your quickstart](/build); its walkthroughs set up the key
and account values the guides use.

The reference lists the public routes and the routes your integration can call with an API key.
Each endpoint describes its authentication and any scopes it requires.

## Find an endpoint

| Reference group | What it covers | Read the guide first |
| - | - | - |
| Market data | Instruments, symbols, price history, quotes, live streams, news and the economic calendar. | [Market data](/guides/market-data-overview) |
| Trading | Orders, account state, exit plans, risk controls and evaluation programs. | [Trading](/guides/trading-overview) |
| Connect | The catalog, Connect links and the routes hosted Connect uses. | [Connect](/guides/connect-overview) |
| Venues | Venue configuration, issued accounts, groups, routes, providers, stages, hedging, webhooks and pre-registration. | [Run a venue](/guides/run-a-venue) |

Hosted Connect uses its own session routes after your backend creates a Connect link.
Use the [Connect SDK](/sdks/connect) to open it and handle its events on your website.

## Use the right key

| Your request is for | Use |
| - | - |
| Your own accounts and their market data or orders | Your Trading API key. |
| A Connect app's trader and their accounts or orders | The app's Connect API key, with the trader's id in `x-trdrs-trader`. |
| A venue's configuration, issued accounts or webhooks | The venue's Venue key, with the endpoint's required scopes. |
| Reading or routing a venue trader's orders | The Venue key with `trader:read` or `trader:trade`, and the trader's id in `x-trdrs-trader`. |
| A venue's Connect pre-registration or integration conformance run | Its pre-registration key. |

[Keys and authentication](/api/keys) covers how you create each key and the routes it reaches.
The signed-in management routes used by the back office and Connect dashboard stay in the
OpenAPI document. Your backend calls the API key routes listed here.

## Choose your environment

Build and test with `https://sandbox.trdrs.co`. Production uses
`https://app.trdrs.co`, with its own keys and accounts. Follow the
[sandbox guide](/sandbox#move-to-production) for the production access steps that apply to your
integration.

Both environments serve their current OpenAPI document:

* [Sandbox OpenAPI document](https://sandbox.trdrs.co/docs/openapi.json)
* [Production OpenAPI document](https://app.trdrs.co/docs/openapi.json)

Use the document for the environment you're targeting when generating a client or checking
request and response types.

## Next steps

<CardGroup cols={2}>
  <Card title="Choose your quickstart" icon="rocket" href="/build">
    Set up your key and make your first sandbox request.
  </Card>

  <Card title="Keys and authentication" icon="key" href="/api/keys">
    Check what your key can call and how to send it.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/api/errors">
    Handle failures by their status, error code and retry rules.
  </Card>

  <Card title="Streaming" icon="tower-broadcast" href="/api/streaming">
    Read live updates and recover account state after a reconnect.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.