Create a key to copy examples filled with your team.

Sending emails

Transactional mail over SMTP, HTTP inject, or the REST send API.

PostShiba sends transactional mail. After the domain verifies, send from any address at that domain. There is no sender identity to create. The cluster must be sending_ready.

Transports

  • SMTP on port 587 with STARTTLS and AUTH PLAIN.
  • HTTP inject at POST {http_endpoint}/api/inject/v1 with HTTP Basic. Use the SMTP username and password.
  • REST send at POST /api/v1/teams/:team_id/clusters/:cluster_id/sends with a Bearer token.
Field Notes
from Required. Must be a verified domain.
to / cc / bcc Recipients.
reply_to Optional Reply-To.
subject Subject line.
text / html Body. Send one or both.
attachments [{filename, content_type, content}]. content is base64.
headers Extra headers. Reserved names are ignored.
unique_args JSON object. Becomes X-Capsule-Unique-Args, is stripped, and comes back on webhooks. X-SMTPAPI unique_args works the same way.
tenant Optional tenant id or slug.

About

PostShiba is the transactional email platform that powers Bento behind the scenes. You can build your own products, like Bento, on top of it.

© 2026 PostShiba by Backpack Internet Pty. Ltd. All rights reserved.

The same policies that govern Bento are applied to PostShiba Privacy | Terms | Security