Getting Started
Sandbox Environment
Test keys (ss_test_…) validate read integrations against the same v1 API.
What sandbox gives you
- Same request contract — use the same base URL, parameters, and response envelopes as production reads.
- Same API, same filters, same response shapes — test keys call the same v1 endpoints as live keys, so integration code does not need a separate base URL.
- Zero-credit reads — test-key entity reads return sandbox data and charge zero credits.
- Write protection — test keys cannot mutate tags or review/data flags.
- Production-only lookalikes —
POST /v1/lookalikesrejects test keys with400 PRODUCTION_KEY_REQUIREDand charges zero credits.
What's different from production
| Sandbox | Production | |
|---|---|---|
| Data | Sandbox entity data | Live v1 entity data |
| Records | Plan-limited | Plan-limited |
| Credits | 0 | Per-row cost |
| Rate limit | 10 req/min | 60 req/min per key |
| Page size | Max 100 | Max 500 |
| Daily row cap | Plan-limited | 10,000 rows/day |
| Export | Available with test-key row cap | Available |
| Tags/flags | Writes blocked | Available with write scopes |
| Lookalikes | Not available | Available with matching read scope |
Safe to reproduce examples
Test-key reads charge zero credits. Use them to compare modes, formats, filters, and pagination before switching to production data.
Switching to production
Replace your ss_test_ key with your ss_live_ key. No code changes are needed for sandbox-supported read paths. Live keys can access lookalikes and perform production-only metadata and write operations when they include the relevant scopes.
Build with sandbox first
Sandbox keys are the safest way to validate request shape, pagination, filters, and response handling before spending production credits.
Need a key?
Keys are issued by our team, not a signup form. Book a 25-minute walkthrough and you'll leave with sandbox and live credentials.