Sandbox vs Production
AfriRoute separates sandbox and production so you can test request shape, error handling, and webhook handling before sending live traffic.
Environment Summary
| Environment | Base URL | Use For | Delivery | Billing |
|---|---|---|---|---|
| Sandbox | https://api.afriroute.ai with a sandbox-scoped key | Development and validation | Simulated or restricted | Not charged as live traffic |
| Production | https://api.afriroute.ai with a production-scoped key | Approved live traffic | Real recipients | Charged to your account |
Use the same public API shape in both environments. The key scope and account approval determine whether a request is sandbox-only or production-enabled.
Configure Safely
AFRIROUTE_API_BASE_URL=https://api.afriroute.ai
AFRIROUTE_API_KEY=YOUR_SANDBOX_OR_PRODUCTION_KEY
Keep these values in your secret manager or deployment environment. Do not hardcode them in frontend code.
Promotion Checklist
Before switching a workflow to production:
- Use a production-approved account and project.
- Confirm the API key has only the required scopes.
- Register and approve sender IDs where required.
- Configure production webhooks over HTTPS.
- Verify webhook signatures.
- Confirm billing and wallet settings.
- Test retry handling for
429and5xx.