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

# Sandbox

> Build and test without touching a real company

The sandbox is a dedicated staging company and a separate, staging-only App
registration, so you can build and test your integration without posting
into anyone's real Workchats.

## Getting access

Sandbox access is set up by Octogle alongside your App registration — see
the first step of the [Quickstart](/getting-started/quickstart). You get:

* a sandbox company to install into
* a staging `client_id` / `client_secret` for that App registration
* an OAuth redirect URI and (from Phase 1b) callback URL pointed at your
  staging environment, not production

## What's different from production

| | Sandbox | Production |
| - | - | - |
| API base URL | `https://public-api.staging.workchats.com` | `https://public-api.workchats.com` |
| Bot token prefix | `wc_bot_test_…` | `wc_bot_live_…` |
| Company | A dedicated staging company | Any company that installs your App |

Everything else — endpoints, error codes, rate limits, the response shapes —
is identical. There's no separate "test mode" flag; the sandbox is a real
company and a real App registration, just isolated from production data.

## The Reference playground

The [API reference](/reference/overview)'s interactive playground is wired
to `https://public-api.staging.workchats.com` only. Paste a sandbox bot
token into it and every request you send there lands in the sandbox
company — it can't reach production.

## Before you go live

Repeat your OAuth install and Quickstart flow against production with your
production `client_id` / `client_secret`, and confirm your App handles a
`wc_bot_live_…` token correctly. Nothing else changes.