Transactional email infrastructure

Transactional email infrastructure for SaaS products and platforms.

Send product email from your own domains—or organize customer-owned domains and senders under one account—with a focused REST API, explicit DNS readiness, durable queues, retries, and delivery history.

Request access Read the docs

Controlled onboarding · Transactional and permission-based traffic only.

POST /v1/emails202 Accepted
{
  "from": "security@acme.app",
  "to": "customer@example.net",
  "subject": "New sign-in detected",
  "content": { "plain": "Review this activity." }
}
em_7kR4…queueddurably accepted
One infrastructure layer

Two ways to build on Tenvio.

Use the same account-level model whether email belongs to your own product or to the businesses your platform serves.

01

For your own product

Operate multiple product domains and sender identities for authentication, billing, security, and workflow notifications.

your appdomainssenders
02

For your platform

Provision customer-owned domains and senders programmatically with scoped Management API credentials and stable external IDs.

your platformcustomer domainssenders
The SMTP problem

A successful API call is only the start.

Transactional mail crosses DNS, queues, retries, transport policy, and recipient infrastructure. Treating that path as a black box leaves product teams guessing when users are waiting.

BeforeRequest accepted?
With Tenvioqueuedsendingaccepted

Explicit state, SMTP outcomes, safe diagnostics, and timestamps—without claiming inbox placement.

Domains are first-class

One account. Multiple sending identities.

Add domains independently, follow the exact DNS records each one needs, and attach multiple senders to the right domain. A sender’s effective state follows its own configuration and its domain’s readiness.

  • 2 domains on the Free plan
  • 3 senders per account
  • Up to 3 senders per domain
  • Independent domain and sender state
DOMAINS2 of 2 used
A
acme.app3 senders · checked 2 min ago
Ready
C
customer.example1 sender · DNS action required
Verifying
DNS READINESS · CUSTOMER.EXAMPLE2 of 3 checks passing
Ownership_tenvio-verificationPassed
DKIMtenvio1._domainkeyPending
DMARC_dmarcPassed
DOMAINcustomer-a.comready
billing@alerts@
DOMAINcustomer-b.ioverifying
notifications@
For platforms

A resource model built beyond one domain.

The multi-domain, multi-sender foundation is live. It can represent domains your company owns or domains your customers own without legacy single-domain branches.

Management APILive · controlled onboarding

Create separate mg_live_ keys with exact scopes for account and usage reads, plus domain and sender operations. DNS actions use the domain scopes. Sending remains isolated behind tv_live_ keys.

Read the Management API guide
Direct delivery

Your application to the recipient MX.

Tenvio operates the delivery path instead of forwarding sends to another email API provider.

01Your applicationAuthenticated API request
02Tenvio queueDurable intake + idempotency
03Delivery enginePolicy + retries
04Recipient MXSMTP outcome
A deliberate boundary

Product email with explicit consent.

Critical and transactional messages are available to every plan. Permission-based broadcast requires a paid Custom plan and separate manual approval.

Available

  • Verification and authentication
  • Security and account alerts
  • Receipts and order updates
  • Approved permission-based broadcast

Prohibited

  • Cold outreach
  • Purchased recipient lists
  • Traffic without documented consent
Delivery lifecycle

Every state means something precise.

queued

Durably accepted for delivery.

sending

An attempt is in progress.

deferred

A temporary failure will retry.

accepted

The recipient SMTP server accepted it.

bounced

The recipient server rejected it permanently.

failed

Delivery ended without acceptance.

Accepted does not guarantee inbox placement. The receiving system controls filtering and final presentation.

Developer API

One explicit send contract.

Create an API key, keep it server-side, and send through the live REST endpoint. Every logical email requires an idempotency key so retries do not create duplicate messages.

POSTEnqueue an email
GETList email history
GETInspect email detail
Read the complete API reference
Send a transactional email
curl -X POST https://api.tenvio.email/v1/emails \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 7f4d9b98-63a8-4c43-a958-41d641fe2fd2" \
  -d '{
    "from": "notifications@yourdomain.com",
    "to": ["user@example.com"],
    "cc": [],
    "bcc": [],
    "type": "transactional",
    "subject": "Your account is ready",
    "content": { "plain": "You can now sign in." }
  }'
Scale with guardrails

Clear limits. Account-level control.

Free includes exact recipient-email quotas and safety limits. Purchased Custom capacity remains subject to abuse, reputation, and infrastructure safety restrictions.

2domains
3senders
3senders / domain
3,000recipient-emails / rolling 30 days
250active delivery jobs

Also enforced on Free: 30 recipient-emails per rolling minute, 300 per hour, and 300 per rolling 24 hours.

Pricing v1

Free and Custom.

Exact USD monthly pricing. Taxes may be additional where applicable.

FREE

$0 / month

Critical and transactional REST API email: 3,000 recipient-emails per rolling 30 days, 2 domains, 3 senders total and per domain, one sending key, 250 active deliveries, and 14-day history. Broadcast is disabled.

CUSTOM

From $10 / month

Choose 10,000 to 2,500,000 recipient-emails and capacity for up to 10–1,000 managed domains. Hard Cap is the only exhaustion mode. Permission-based broadcast requires separate manual approval.

Build and review exact pricing
Controlled onboarding

A focused product email surface.

Available

  • Critical and transactional REST Email API
  • Multiple domains and senders
  • BCC input with address-private history
  • Approved Custom permission-based broadcast
  • Free and Custom Hard Cap plans

Policy boundary

  • Explicit recipient permission
  • Documented audience source
  • No cold outreach
  • No purchased lists
FAQ

The infrastructure, without the ambiguity.

What is Tenvio?

Tenvio is product email infrastructure for critical, transactional, and separately approved permission-based broadcast traffic.

Can one account use multiple domains and senders?

Yes. The Free plan supports 2 domains and 3 senders across the account, with up to 3 senders on one domain.

Does “accepted” mean delivered to the inbox?

No. It means the recipient mail server accepted the message. The receiving system controls filtering and inbox placement.

How is broadcast enabled?

A paid Custom plan is necessary but not sufficient. Tenvio separately reviews permission and risk controls before an operator approves broadcast capability. Payment never grants approval.

Can I use a purchased list or send cold outreach?

No. Both are prohibited. Broadcast recipients require a documented permission basis and audience source.

Request access

Tell us what your product needs to send.

Tenvio is onboarding SaaS products and platforms during controlled onboarding. Share your domain model, transactional use case, and expected volume.

Keep secrets out of this form.Do not include API keys, passwords, recipient lists, or message payloads.
Describe the transactional messages and how domains belong to your product or customers.