Mail guide
Send transactional email through Vorynza Mail. Quickstart, plans, delivery logs, and security.
Vorynza Mail is a transactional email service powered by AWS SES. Add a verified sending domain, create an API key, and start sending in minutes.
Quickstart
1. Create a mail service
In your project dashboard, navigate to Mail and create a service. Choose a plan that fits your monthly send volume. The service provisions in a few seconds.
2. Add a sending domain
Add the domain you want to send from (e.g. mail.yourcompany.com). Vorynza generates DKIM, SPF,
and DMARC DNS records that you need to add to your DNS provider.
See the domain setup guide for full details on DNS records, auto-configuration, and verification.
3. Create an API key
Create an API key with the mail:send scope. The key is shown once — copy it immediately.
See the API keys guide for details on key format, scopes, and revocation.
4. Send your first email
curl -X POST https://api.vorynza.cloud/v1/mail/send \
-H "Authorization: Bearer vnz_mail_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"from": "hello@mail.yourcompany.com",
"to": ["user@example.com"],
"subject": "Hello from Vorynza Mail",
"text": "This is a test email.",
"html": "<p>This is a test email.</p>"
}'See the sending guide for the full API reference, request fields, and message statuses.
Plans and limits
| Plan | Monthly price | Emails/month | Domains | API keys | Log retention |
|---|---|---|---|---|---|
| Launch | ₦12,000 | 10,000 | 2 | 3 | 7 days |
| Growth | ₦30,000 | 50,000 | 10 | 10 | 30 days |
| Business | ₦75,000 | 200,000 | 25 | 25 | 90 days |
Plan limits apply per mail service. Monthly send counts reset on your billing date.
If you exceed your plan's monthly send limit, sending is paused until the next billing cycle or until you upgrade to a higher plan.
Delivery logs
Every message sent through Vorynza Mail appears in the delivery logs. Logs show:
- From address and recipients
- Subject line
- Current status and timestamps
- Error messages for failed deliveries
- Provider message ID for debugging
Logs are searchable by status and paginated by cursor. Retention depends on your plan.
Suppression handling
Recipients that bounce or complain are automatically suppressed. Future send attempts to suppressed addresses are rejected before reaching the provider.
Security
- API keys are SHA-256 hashed before storage
- Connection strings and credentials are never logged
- Send API keys are validated with constant-time comparison
- Provider event webhooks are authenticated with HMAC signatures
- All email content is encrypted in transit (TLS)
Need help? Contact support. Something missing? Let us know.