orboto Mail

Transactional email is the mail your application sends because something happened - a signup confirmation, a password reset, an invoice, a workflow notification. It is different from marketing email (newsletters, campaigns) in one important way: each message is triggered by one user's action and that user expects to receive it. Getting it delivered reliably requires infrastructure most teams would rather not build themselves: a sending service with a good reputation, DKIM/SPF/DMARC configured correctly, bounce and complaint handling, and a record of what was sent.

orboto Mail (internally "OMS") is that infrastructure, run for you. It is a standalone product - any application can send through it, with or without an orboto workspace - built on Amazon SES with EU-only data residency (Frankfurt + Dublin), and it plugs directly into an orboto workspace's outbound email (invites, notifications, password resets) with a single click. See Using orboto Mail from an orboto workspace for that specific path; the rest of this section documents orboto Mail as a product on its own.

What you get

• A single send API. POST /v1/send takes a from-address, a recipient, and either raw HTML/text or a server-side template, and hands the message to SES across two EU regions with automatic failover. See Sending email.
• Batch sending. POST /v1/send/batch sends up to 100 messages in one call instead of looping client-side.
• Server-side templates. Store a subject + HTML/text body with a JSON-schema-validated set of variables, then send by referencing the template's id instead of re-sending the markup every time. See Templates.
• Verified sending domains. Add your own domain, publish the DNS records orboto Mail gives you, and send as you@yourdomain.example with DKIM, SPF, and DMARC all correctly aligned. See Sending domains and DNS.
• Suppression list + delivery events. Hard bounces and spam complaints are automatically added to a per-account suppression list and excluded from future sends; every bounce, complaint, delivery, and quota event can be pushed to your own webhook endpoint. See Suppression and delivery events.
• A monthly quota with clear failure modes. Every account has a monthly sending quota; GET /v1/quota reports current usage, and a send that would exceed the quota fails with a specific, actionable reason instead of a generic error.
• Attachments, CC/BCC, and tags. Up to 20 attachments and 30 MB per message, up to 50 CC and 50 BCC recipients, and a free-form tag bag on every send for your own reporting.
• Optional open tracking. Per sending domain, you can opt in to a tracking pixel that records opens - off by default, since it touches recipient privacy.

Two ways to use it

Both paths hit the same API and the same account - the workspace integration is a connect-once shortcut, not a different product.

Account and dashboard

There is no dashboard on mail.orboto.io itself - that host is the API endpoint plus this documentation. Your account, billing, API keys, sending domains, templates, suppression list, and webhook subscriptions are all managed at account.orboto.io/mail once you've signed up.

orboto Mail is a cloud-only service - there is no self-hosted deployment. If you self-host orboto itself, you still reach orboto Mail over the public API exactly like any other application.

Troubleshooting