Environments
Who this is for: every integrator. When to use it: when configuring base URLs and credentials. What happens next: you'll point your code at the right host for each stage.
Zamplia provides separate environments per side of the marketplace. Always build and validate against the test environment first, then switch the base URL and credentials for production. Endpoint paths, fields, and payloads are identical across environments — only the host changes.
Demand API
| Stage | Base URL | Credentials |
|---|---|---|
| Staging / Sandbox | https://zampliabackend-staging.azurewebsites.net | Staging bearer token |
| Production | https://zamplia.zamplia.com | Production bearer token |
Supply API
| Stage | Base URL | Credentials |
|---|---|---|
| Sandbox | https://surveysupplysandbox.zamplia.com/api/v1/ | Sandbox ZAMP-KEY |
| Production | https://surveysupply.zamplia.com/api/v1/ | Production ZAMP-KEY |
Recommended setup
Keep the host in an environment variable so promoting from test to production is a one-line change:
# .env (Supply example)
ZAMPLIA_BASE_URL=https://surveysupplysandbox.zamplia.com/api/v1/
ZAMPLIA_API_KEY=your_sandbox_key
caution
Test and production credentials are not interchangeable. A token or key issued for one stage will be rejected by the other.
Next: validate end to end in the Sandbox.