Stop worrying about deliverability.
Transactional and campaign email from the same account - message streams, sender verification, bounce handling, and delivery tracking, all real, all yours to inspect.
curl -X POST https://api.finomium.co/api/v1/send \
-H "Authorization: Bearer $API_TOKEN" \
-d '{
"from": "billing@yourapp.com",
"to": "customer@example.com",
"templateId": "invoice-receipt",
"templateModel": { "amount": "$42.00" }
}'
# {"messageId":"7f3e...","status":"queued"}Message streams
Transactional, broadcast, and inbound mail live in separate streams - so one bad campaign never puts your password-reset emails at risk.
Sender verification
Verify a sending address by confirmation link, generate real DKIM keys, and check SPF/DKIM/CNAME live against DNS.
Bounce handling
Bounces are ingested straight from your mail server's own logs - filterable, actionable, not a black box.
Suppression lists
Checked before every single send, at both the account and the campaign level - once suppressed, always respected.
Delivery tracking
Real open and click tracking through pixel and redirect endpoints, not estimated or sampled.
Per-server tokens
Issue a dedicated API token per sending server or app, so one compromised key never exposes everything.
Templates & campaigns
Reusable transactional templates with variable substitution, plus draft-to-launch campaigns with segment targeting and async batch sending.
AI-assisted send times
Subject-line and send-time recommendations grounded in your own account's real open-rate history - via a self-hosted model, so your data stays on your infrastructure.
Not just outbound - a real inbound pipe
Inbound is its own message stream, with a real ingestion pipeline off your mail server: MIME parsing, searchable storage, and retry/bypass handling - so replies and support inboxes are a first-class citizen, not an afterthought bolted onto a sending API.