Deliverability · Email

This page maps the shared deliverability model onto email: which records prove your identity, how dedicated IPs isolate your reputation, and where to watch for trouble. Each section links to the page that covers the mechanics in full; go there for the record shapes, API payloads, and edge cases.

Email authentication is per organization, even on a shared domain. We generate a DKIM signing key for your organization and provide its public half under a unique selector. You also publish a return-path CNAME that routes bounces through us and provides SPF alignment, plus a DMARC record that defines your policy for authentication failures.

The send gate is DKIM + return-path + DMARC. A domain sends only once all three verify. The fourth record, the tracking CNAME for branded open and click tracking, is separate and optional: it gates branded tracking, never sending.

By default your mail rides the Shared Bird.com Pool, our shared sending infrastructure, and that stays your default until you explicitly change it. Dedicated IPs are the opt-in alternative: addresses only your organization sends from, organized into org-scoped pools that every workspace can use. Two safeguards protect you from a cold IP. New IPs warm automatically with overflow routed through the shared pool, so your volume never drops. The default-pool rules also stop you from pointing unrouted traffic at a pool with nothing ready to send.

Per send, choose a pool with the optional ip_pool_id field on the send request; omit it to use your default.

Bounce and complaint events show which addresses fail and which recipients report your mail. The suppression list stops repeat sends to hard bounces, complaints, and unsubscribes before they leave the platform. Monitor aggregate delivery, open, and click rates in Email > Metrics. Use the email log to inspect a specific send. To inspect the SPF, DKIM, and DMARC results recorded by a recipient's mailbox, paste the message source into the Email header analyzer.

Two adjacent things to know: BIMI, your logo in supporting inboxes, is a DNS record you publish yourself rather than something we manage for you, and our v1 API has no blocklist-status endpoint.