Documentation
Sign inGet started
Get started
Guides
API Reference
SDKs
CLI
Knowledge Base
Changelog

Sending from the shared domain

Every new Bird workspace can send test email from Bird's shared onboarding domain, using onboarding@messagebird.dev. It requires no DNS records or domain verification.
Because the domain is shared by everyone, it comes with deliberate guardrails. This page explains what they are and why they're there.

What it's for

The shared domain is a test and first-send capability:
  • Confirming your account and workspace can send, right after signup.
  • Letting a developer verify an integration end to end before your own domain is verified.
  • Running deterministic delivery tests against the mail sandbox.
Its recipient restriction and daily cap make it unsuitable for production traffic.

The guardrails

Recipients must be verified members of your workspace. The shared domain delivers to verified Bird accounts with access to the workspace. Bird rejects other recipients, except sandbox addresses.
A daily recipient cap applies. By default, the shared domain allows 50 recipients per organization per UTC day. Bird rejects further recipients until the next UTC day.
Sandbox addresses are an exception. Addresses such as delivered@messagebird.dev and bounce@messagebird.dev are exempt from the members-only restriction, so you can simulate outcomes without inviting anyone. They still count toward the daily cap. See Test email delivery.

Moving to production: verify your own domain

To send production email, set up your own sending domain. This removes the shared domain's recipient restriction and daily cap and lets you build reputation on your domain. The Sending domains guide covers registration, DNS records, and verification.
The shared domain remains available for testing after you verify your own domain.

Next steps