Quickstart
Create an inbox and send your first email in under five minutes.
Authentication
API keys, the base URL, and how requests are authenticated.
Receiving email
Get inbound mail and delivery events delivered to your endpoint.
API Reference
Every endpoint, request body, and response schema.
What you can build
- Support & sales agents that own a dedicated inbox, triage incoming mail automatically, and reply in-thread so conversations look native in any mail client.
- Per-user inboxes — provision a fresh address for every customer, task, or workflow in a single API call, and delete it when the work is done.
- Transactional senders — deliver invoices, receipts, and alerts with deliverability already handled: no SMTP configuration, no reputation management.
- Anything that reads or writes email — without standing up SMTP or IMAP infrastructure, managing MX records, or worrying about shared-IP reputation.
How it works
Create an inbox
POST /inboxes returns an address like support-bot@mail.sentvia.ai — live immediately on the shared domain, ready to send and receive. No DNS setup required.Send & receive
Send with
POST /messages. Inbound mail is parsed, threaded, and either POSTed to your webhook on the message.received event or available via GET /messages.Deliverability, handled
Every Sentvia domain ships with SPF, DKIM, and DMARC already configured. Automatic bounce and complaint suppression keeps your sender reputation clean, and higher-tier plans include reputation isolation so traffic from one workspace can’t affect another. You focus on what the agent does; Sentvia keeps the mail landing in the inbox.Base URL:
https://sentvia-api-production.up.railway.app/v1. All requests are authenticated with a Bearer API key — see Authentication.