Overview
VeloxStack Mail gives every tenant in your SaaS an inbox identity, custom-domain support, outbound delivery, and inbound reply routing through one API model.
Documentation
Modern docs for teams building email into their product
Start with one endpoint, then layer in domains, inbound replies, and webhook-driven thread updates as your integration matures.
Quickstart
Create a tenant, connect a domain, and send your first message in a few steps.
1. Create tenant
Provision a workspace-scoped inbox container for one customer.
2. Verify domain
Add DNS records for the sender domain your customer wants to use.
3. Send message
Post JSON to `/v1/send` and watch delivery plus replies flow back.
Authentication
Authorization: Bearer mf_test_9f2d...
Content-Type: application/jsonSending Email
Send branded tenant email through one request.
POST /v1/send
{
"tenant_id": "acme",
"from": "support@acme.com",
"to": "user@customer.com",
"subject": "Your inbox is live",
"template": "launch_notice"
}Receiving Replies
Incoming messages are normalized into reply events so your app can update tenant threads, agent views, or CRM records without parsing raw mailbox data.
Domains
Store verified domains per tenant and expose DNS instructions in your onboarding flow. Each sending identity remains scoped to the customer who owns it.
Webhooks
VeloxStack Mail emits delivery, bounce, and inbound-reply events for your backend.
message.received
{
"type": "message.received",
"tenant_id": "acme",
"thread_id": "thr_20481",
"from": "user@customer.com",
"to": "support@acme.com"
}