Appearance
Sandbox vs Production
Sendivent has two environments. The environment is determined by your API key prefix.
API Key Prefixes
| Prefix | Environment | Base URL |
|---|---|---|
test_* | Sandbox | https://api-sandbox.sendivent.com |
live_* | Production | https://api.sendivent.com |
What's Different
| Sandbox | Production | |
|---|---|---|
| Rate limit | 10 req/sec | 100 req/sec |
| Daily quota | 150 | Per plan |
Data isolation
Shared across environments:
- Integrations (channel configurations)
- Senders (verified email addresses, phone numbers)
Separate per environment:
- Events
- Templates
- Contacts
You'll configure events and templates twice — once for sandbox, once for production.
Real delivery (no mock mode)
Both environments send actual notifications. If you use a real email with a test_* key, it will be delivered.
To avoid sending real emails during development:
- Use your own email to verify delivery works
- Use
test@example.com(won't route anywhere)
When to Use Each
| Use Case | Environment |
|---|---|
| Local development | Sandbox (test_*) |
| CI/CD tests | Sandbox (test_*) |
| Staging | Sandbox (test_*) |
| Production app | Production (live_*) |
Switching Environments
Change both your API key AND base URL:
bash
# Sandbox (development)
SENDIVENT_API_KEY=test_your_key
SENDIVENT_API_URL=https://api-sandbox.sendivent.com
# Production
SENDIVENT_API_KEY=live_your_key
SENDIVENT_API_URL=https://api.sendivent.comCommon Mistakes
- Wrong URL for key type —
test_*keys only work withapi-sandbox.sendivent.com - Real emails in sandbox — They WILL be delivered
- Hardcoding keys — Use environment variables
See Also
- Authentication — How to use API keys
- API Overview — Rate limits and errors