Live and sandbox
Build and test with a sandbox key, on data kept apart from your real projects, then switch to a live key.
Every key belongs to one of two environments. There is one base URL for both: the key decides.
| Live | Sandbox | |
|---|---|---|
| Projects, folders, products | Your real ones | Kept apart: a sandbox key sees only sandbox ones, a live key never sees them |
| Members of your organisation | Real | The same real members |
| Guest projects (Open Guest) | Counted and billed | Never counted or billed |
| Usage figures on the Developer page | Counted | Not counted |
| Embeds | Open live projects | Do not open: sandbox projects cannot be embedded |
| Signing in as a member | Allowed | Refused |
| Tokens | Live | Sandbox |
How to tell which a key is#
The Developer page shows each key under its environment. The token endpoints also say it in their answer:
{"token": "…", "expiresOn": 1792345678000, "environment": "sandbox"}What is shared#
Members, subscriptions, keys, settings and webhooks belong to the account, not to an environment. That is what lets a sandbox project be owned by a real member.
Moving to live#
- Create a live key with the same access as your sandbox key.
- Replace the key in your server's configuration.
- Anything you made in the sandbox stays there. Create your real projects, folders and products with the live key, or in the app.