Get Started
Environments
Understand the difference between live and sandbox before issuing keys or sending traffic.
Atlas supports two public environments.
| Environment | Base URL | Key prefix | Data profile |
|---|---|---|---|
| Sandbox | https://sandbox-api.rangler.co/v1 | atl_test_ | Safe development and integration validation |
| Live | https://api.rangler.co/v1 | atl_live_ | Production customer traffic |
Environment rules
- Sandbox keys only work on sandbox.
- Live keys only work on live.
- Data-plane traffic is isolated by environment.
- Webhook endpoints and subscriptions are managed at the organization level in the portal. Review their targets and rules before enabling live traffic.
What sandbox is for
- validating request signing and authentication
- testing error handling and retry behavior
- verifying webhook receivers before production
- developing customer-facing notification flows
What live is for
- production delivery to your customers
- real operational usage and metering
- production traffic and escalation workflows
Common mistakes
- using an
atl_test_key againstapi.rangler.co - assuming webhook endpoints or subscriptions are partitioned by environment in the portal
- copying examples from the wrong environment tab in the portal or docs