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

# Build a business

> Create a venue, prove your Venue key works, and choose the back-office tool or your own backend.

A venue holds your branding, providers, groups and accounts. Use a **Venue key** to manage it
from your backend. The back-office tool is a ready-made client of those APIs; you can also build
your own business software directly.

## 1. Create or select your venue

Sign in to [sandbox API access](https://sandbox.trdrs.co/settings/api). Choose the venue setup,
create or select a venue, and create a Venue key with the scopes your integration needs. Save
its venue ID and store the secret on your server when shown.

Venue creation, owners and key management stay in your first-party TRDRS account. An installed
back office cannot use a Venue key to give itself more authority.

## 2. Read your venue

```bash theme={null}
export TRDRS_API_BASE_URL=https://sandbox.trdrs.co
# Set TRDRS_VENUE_ID and TRDRS_VENUE_KEY in your server-side environment.
curl --fail-with-body "$TRDRS_API_BASE_URL/api/partner/venues/$TRDRS_VENUE_ID" \
  -H "Authorization: Bearer $TRDRS_VENUE_KEY"
```

Expect HTTP **200** with your venue. This request requires `venue:read`. Your key cannot read a
venue owned by someone else, and a sandbox key cannot authenticate in production.

## 3. Choose your tool

<CardGroup cols={2}>
  <Card title="Install the back office" icon="download" href="/guides/back-office">
    Run the business UI yourself. Connect its server to your sandbox venue and keep the Venue key out of the browser.
  </Card>

  <Card title="Use your own backend" icon="code" href="/guides/run-a-venue">
    Configure and operate the same venue through the documented API. No back-office installation is required.
  </Card>
</CardGroup>

The existing [hosted back office](https://sandbox.trdrs.co/developer) remains available while
you move to the tool. Opening it does not migrate your older accounts into new groups.

## 4. Exercise a complete sandbox workflow

Use a dedicated test trader and account, not an existing customer account.

1. Set your venue name, description and logo.
2. Configure instruments and conditions, then a group with a paper-book route.
3. Have your test trader sign in to sandbox. Then, as the venue owner, issue an account
   into that group using the trader’s sign-in email.
4. Open the trading app as that trader and check its branding and effective rules.
5. Test trading deliberately, then inspect analytics and stage eligibility. Advance only when
   the documented conditions and completeness checks pass. Retry with the same request identity.

[Run a venue](/guides/run-a-venue) carries configuration details;
[Venue accounts](/guides/venue-accounts) and [analytics](/guides/firm-analytics) cover the
account lifecycle. The [integration self-check](/partner-platform/conformance/test-evidence)
tests client behavior; it does not replace verification of your business rules.

## What stays separate

Your checkout, subscriptions and payments are yours. Sandbox does not require payment setup.
A Venue key does not authorize personal trading. Provider integration and production listing
are separate from creating a venue; [Connect](/guides/connect-overview) explains those boundaries.