Concepts
Understand how Samva's email API is designed — the data model, the unified send shape, tenancy, and what drives deliverability.
The guides and reference show you what to type. This section is about why Samva works the way it does. Reading it is optional, but it pays off: once the model clicks, the API stops feeling like a list of endpoints and starts feeling like one coherent system.
Samva is an email API for developers. The design choices here — a single send path, organization-scoped data, domain-level authentication — were made for email first. They also leave room for the channels that come next, which is why a few names (like the "unified" send shape) read as more general than email alone.
Email first. Samva is launching with email. SMS, WhatsApp, and voice are staged and will be documented as they ship.
How Samva works
The path an email takes from your send call to a recipient's inbox, and the pieces involved along the way.
Email and the unified API
Why there's one message model, two ways to send, and what the channel-aware shape is preparing for.
Authentication and tenancy
How API keys identify you, how organizations isolate your data, and why every record is tenant-scoped.
API keys and OAuth sessions
The two ways to authenticate — durable keys for servers, OAuth sessions for people — and how each picks the organization.
Deliverability
What makes email reach the inbox — domain authentication, sender reputation, and engagement signals.