Environments
Every API key belongs to exactly one environment.
| Environment | Key prefix | Purpose |
|---|---|---|
Sandbox |
did_test |
Development and testing |
Production |
did_live |
Real credentials and real holders |
The prefix is visible in the key itself, so you can tell at a glance — in a terminal, a screenshot, a support ticket or a code review — which environment a key belongs to.
Isolation
Sandbox and Production are separate logical environments within the shared platform. Sandbox data and
configuration are isolated from Production. A key cannot cross between them: presenting a Production key with a
did_test prefix (or the reverse) is rejected, because it means the caller believes they are somewhere they
are not.
Dedicated infrastructure for a tenant is a deployment-tier decision, not part of this boundary.
Promoting to Production
- Build and test against Sandbox.
- Have an administrator create a Production key with the same scopes.
- Deploy the Production key to your secret manager.
- Keep the Sandbox key for continued development — you do not need to revoke it.
Not yet available
Self-service sandbox provisioning and pre-seeded test personas are planned but not implemented. A sandbox is configured for you today.