Samva Documentation
Email API for developers — send transactional and conversational email with a type-safe SDK and REST API
Samva is an email API for developers. You send email through a type-safe TypeScript SDK or a single REST endpoint, manage the contacts you send to, keep replies threaded into conversations, and receive delivery and inbound events over webhooks.
This documentation is organized into four kinds of material, each answering a different question. If you are new, start with Get started and work through your first send. When you have a specific job to do, reach for a Guide. When you need exact field names, signatures, and status codes, consult the Reference. When you want to understand why Samva is shaped the way it is, read the Concepts.
Email first. Samva is launching with email. SMS, WhatsApp, and voice are staged and will be documented as they ship.
Find your way
Get started
A guided tutorial for your first send. Begin here if you are new to Samva.
Guides
Task-focused how-tos: send an email, verify your domain, receive webhooks, use the CLI, and connect AI agents.
Reference
Authentication, the TypeScript SDK, the REST API, and SMTP — exact parameters and behavior.
API reference
Per-operation REST documentation generated from the OpenAPI spec.
Concepts
How Samva works, the unified API model, tenancy, and deliverability — the why behind the API.
How the SDK and REST API relate
There are two ways to send the same email. The TypeScript SDK exposes samva.email.send(...), an ergonomic wrapper that flattens email fields like to, subject, and html directly into the request. Under the hood, every send — whether from the SDK or a raw HTTP request — goes to POST /v1/messages. The REST endpoint takes the unified message shape, where the channel is named explicitly and email content is nested under email. The Concepts section explains why both shapes exist and when to choose each.
Support
- Email: support@samva.app