Introduction

PostShiba is an email API for SaaS platforms that send and receive email on behalf of their customers.

Send from your customers' domains, give each customer their own sending controls, and trace every delivery problem from one place. You send over SMTP, HTTP inject, or the REST API, and receive mail into hosted or domain-bound inboxes.

Quickstart

  1. Create an API key in the dashboard. Use a Send only key in your app. Keep Full access keys for setup scripts, the CLI, and MCP.
  2. Add and verify a domain. Sending waits until DKIM verifies.
  3. Choose a send path and send your first message with HTTP, SMTP, the CLI, or an SDK.

Until your account is approved for production, you can send only to your team members' emails, your live inbox addresses, and inbox forward-to addresses. See Does PostShiba require production approval?

Core concepts

Concept What it is
Cluster A named sending environment with a shared sending IP, a monthly capacity plan, an SMTP host, and an HTTP inject URL. Keep transactional and bulk mail on separate clusters.
Domain A sending domain you verify with DKIM. You can send from any address on it.
Tenant One of your customers. Tenants isolate domains, SMTP credentials, inboxes, suppressions, and webhooks.
Inbox An address that receives mail and forwards it or POSTs it to your webhook.
Suppression An address PostShiba won't send to, after a hard bounce, a spam report, an unsubscribe, or a manual add.
Webhook A URL that receives delivery events such as delivered and bounce.

Build something

These guides combine the APIs into complete products.

Learn the basics

New to sending email at scale? Become an email pro with a short, hands-on course. Check your own domain's SPF, DKIM, and DMARC, plan a warm-up for a new IP, pick an IP pool setup, and set up PostShiba the right way.

Next steps