Find clear answers about sending, deliverability, and email campaigns.

Envoyez vers des adresses sandbox documentées telles que delivered@messagebird.dev, bounce@messagebird.dev ou complaint@messagebird.dev. Celles-ci exercent les résultats et les webhooks via le pipeline normal. Limitez votre audience de répétition aux adresses sandbox ; les adresses réelles dans le même envoi reçoivent du courrier réel.

Le domaine d'intégration prend en charge un premier envoi selon ses restrictions documentées, et les adresses sandbox permettent de tester. Vérifiez votre propre domaine d'envoi pour un envoi régulier. Consultez les limites actuelles de votre espace de travail plutôt que de vous fier à un quota fixe de plan indiqué sur cette page.

Utilisez le guide de démarrage premier e-mail pour une intégration API, le guide SMTP pour une application SMTP existante, Email marketing pour les campagnes, ou le guide de démarrage agent-mailbox pour les conversations. Chaque parcours renvoie vers la configuration et la documentation correspondantes.

You can start on the Free plan with its included sending allowance to test integration and delivery. Paid Email plans add a monthly deposit directly to your shared Bird balance, and each email you send is billed from that balance at your plan's published per-email rate without expiring message bundles. Visit the pricing page to compare current deposits, rates, and plan allowances.

If you downgrade your plan, any custom handles you have already claimed continue receiving mail without interruption, and you can claim additional handles once your usage is back within your plan's limit. Mailboxes created on your own verified domain count toward your total mailbox quota without using any of your custom-handle allowance.

Dedicated IPs are available as a monthly add-on on eligible paid Email plans. You can check the current monthly price per IP and the maximum number of dedicated IPs included in each plan tier on the Email pricing page before ordering from the dashboard.

Your sending throughput and monthly allowances depend on your Email plan, with full tier details listed on the Email pricing page and any custom enterprise limits applied automatically. You can check your active rate limits and remaining quota through the API or response headers, and use the returned wait time to pace retries when requests are throttled. API and SMTP traffic share your sending throughput, while batch requests and campaign broadcasts follow their own request limits.

A complete email can be up to 20 MB, including the HTML body, plain text, headers, and encoded attachments. Because attachment encoding adds overhead, keep raw attachment files under 15 MB so the assembled message stays within the limit, and keep in mind that some recipient mail servers enforce smaller size caps.

When content storage is enabled, you can inspect sent message bodies and attachments for up to 30 days. For Agent Mailboxes, parsed headers, extracted text, and attachments stay available for 30, 90, or 365 days depending on the retention tier selected on your plan, while raw MIME payloads are retained for 30 days.

Scope the agent's API key to the specific permissions its workflow requires, and configure mailbox receive rules so untrusted senders do not trigger agent runs. For sensitive outbound communication, have the agent save a draft first so a human or policy check can verify the recipients, sender address, and body before sending.

Oui, les deux passent par la même API d'envoi. La seule différence est le champ category, qui détermine l'application des suppressions et des désinscriptions. Choisissez transactional pour les réinitialisations de mot de passe et les reçus, et marketing pour les campagnes.

Envoyez un en-tête Idempotency-Key avec chaque envoi logique. Si la première requête a réussi mais que vous n'avez jamais reçu la réponse, la rejouer avec la même clé vous renvoie le résultat original avec un en-tête Idempotency-Replay, au lieu d'envoyer l'e-mail deux fois.

Définissez scheduled_at sur un horaire entre 30 secondes et 30 jours dans le futur. L'envoi est immédiatement accepté et reste planifié jusqu'à son expédition, vous pouvez donc l'annuler à tout moment avant.

Oui, en base64 dans le tableau attachments. Pour afficher une image en ligne, attribuez-lui un content_id et référencez-le dans votre HTML avec cid:. Maintenez les fichiers bruts à 15 Mo maximum afin que le message respecte la limite de 20 Mo une fois encodé, et notez que les types de contenu exécutables et de script sont refusés avant l'envoi.

Yes. If your application or third-party software already sends email over SMTP, you can switch to Bird without rewriting code by updating the SMTP host, port, and credentials. Verify your sending domain in the dashboard and authenticate with an API key that has email sending permissions.

Connect on port 465 for implicit TLS encryption, or use ports 587 and 2525 with STARTTLS, including port 2525 for cloud environments that block standard mail ports. Point your client to the regional SMTP host that matches your API key; unencrypted submission on port 25 is disabled.

Use SMTP when you want a drop-in relay for existing services, CRMs, or frameworks that already assemble MIME messages. Choose the HTTP API when you want to send with stored templates, schedule deliveries, or pass structured JSON fields from your application code. Both methods share your verified domains, IP pools, suppression lists, and analytics.

SMTP messages are billed at the same published per-email rates as HTTP API sends under your Email plan, with no extra protocol fee. Check the Email pricing page for current plan rates, or talk with our team if you are migrating a high-volume SMTP workload.

Contacts live in your workspace and can store an email address, a phone number, your own external user ID, and custom attributes. Audiences reference those shared contact records, so when a customer updates their email address or profile details, the change carries across the audiences they belong to.

Upload a CSV, TSV, or Excel file in the dashboard, map your columns to contact attributes, and assign the imported contacts straight to an audience. To keep lists synchronized from your application, you can create or update up to 1,000 contacts per request through the API or CLI.

Audiences use explicit membership that you manage by adding or removing contacts through file imports, the dashboard, or the API. When a scheduled broadcast starts sending, Bird resolves the audience's current members so recent additions and removals take effect automatically.

You can define text, number, boolean, and date-time attributes with optional fallback values for missing data. Those attributes plug directly into your email templates so you can personalize subject lines and body copy for each recipient.

Select a saved audience when setting up your broadcast. When sending starts, Bird resolves the current audience members, filters out suppressed or unsubscribed addresses, and personalizes the template with each contact's saved attributes.

Yes. You can send a broadcast immediately or schedule it up to a year in advance, and you can edit or reschedule the campaign before delivery begins. If you cancel a broadcast that is scheduled or in progress, Bird stops delivery to any remaining recipients.

Broadcasts send a campaign to a saved audience up to a year ahead. For individual transactional emails, the sending API lets you schedule a message from 30 seconds to 30 days in advance. When you schedule a transactional send, Bird locks in the template version, language, and personalization values at request time so later edits do not alter your queued message.

Yes. Create a test audience populated with Bird sandbox addresses to simulate deliveries, bounces, and spam complaints without sending mail to real inboxes. Sandbox sends trigger your webhooks and appear in your analytics so you can verify your webhook and analytics integration before launching a live campaign, and they count toward your sending allowance.

Marketing broadcasts and transactional emails share your verified domains, templates, and delivery infrastructure, so you do not have to sync templates or suppression lists across two separate providers. Marketers can compose and schedule broadcasts in the dashboard, and developers can automate audience updates and campaign setup through the API, CLI, or MCP tools.

When you send a marketing broadcast or tag an API send as marketing, Bird includes one-click list-unsubscribe headers and an unsubscribe link for Gmail and Yahoo compliance. When a recipient opts out, Bird records their preference and filters them out of future marketing sends while still allowing transactional receipts and account alerts through.

Each broadcast report tracks delivered messages, human opens with automated privacy proxy prefetches filtered out, link clicks, bounces, and spam complaints. To tie campaigns back to signups or purchases, include UTM or custom link parameters and measure conversions in your product or analytics tool.

Use broadcasts in the dashboard to send newsletters, product announcements, and scheduled promotions to your saved audiences. For event-driven lifecycle emails such as welcome series, onboarding nudges, or cart reminders, trigger templates directly from your application backend using the Email API.

No. You can write and preview HTML templates in the dashboard code editor, or manage template files from your repository using the API, CLI, and MCP tools. If your team builds templates with React Email, you can compile them to HTML with Bird personalization placeholders intact and sync the output to the same drafts and published versions visible in the dashboard.

Templates use Liquid placeholders to merge dynamic data into subject lines, preview text, and message bodies. When you send a broadcast, Bird populates contact placeholders automatically from each recipient's saved profile attributes and fallback values. When you send transactional emails through the API, you can pass custom parameters such as order numbers or line items and use Liquid conditionals and loops to format the message.

Yes. Edits are saved to a working draft while live traffic continues using your currently published version. When you publish a change, Bird creates a version snapshot, and you can roll back to any earlier snapshot with one click if you spot a mistake, without affecting messages that have already been accepted for delivery.

Yes. A single template can store localized subject lines, preview text, and HTML bodies for multiple languages alongside a default fallback language. You can choose whether sends requesting an untranslated locale fall back to your default language or return an error, and preview each locale with sample recipient data before publishing.

Nous générons les enregistrements pour vous : un enregistrement TXT DKIM pour signer vos e-mails, un CNAME return-path qui aligne SPF (aucun enregistrement SPF apex requis), et un enregistrement TXT DMARC. Un CNAME de suivi pour les liens d'ouverture et de clic brandés est optionnel. Ajoutez le domaine, collez les enregistrements chez votre fournisseur DNS, puis cliquez sur vérifier : la plupart des vérifications aboutissent en quelques minutes après la propagation DNS, bien que cela puisse parfois prendre plus longtemps.

DMARC indique aux serveurs de réception quoi faire avec les e-mails qui échouent à l'alignement DKIM ou SPF, et où envoyer les rapports agrégés montrant qui envoie en tant que votre domaine. Nous exigeons un enregistrement DMARC avant qu'un domaine puisse envoyer, et recommandons de commencer avec p=none, qui surveille sans affecter la livraison. Une fois que vous avez confirmé que toutes les sources légitimes sont alignées, renforcez la politique vers p=quarantine ou p=reject. Si vous publiez déjà DMARC sur votre domaine ou un domaine parent, nous l'utilisons tel quel. Les principaux fournisseurs de messagerie attendent désormais des expéditeurs en masse qu'ils publient une politique, donc en avoir une fait de plus en plus partie des conditions pour atteindre la boîte de réception à grande échelle.

Oui aux deux, et nous recommandons un sous-domaine dédié, car il isole la réputation de vos e-mails de votre messagerie d'entreprise. Vous pouvez également utiliser des domaines séparés pour les e-mails transactionnels et marketing, ou un par marque, chacun avec sa propre authentification et réputation.

Envisagez une IP dédiée si vous envoyez un volume régulier et souhaitez contrôler votre propre réputation IP. Un expéditeur à faible volume ou irrégulier sera mieux servi par le pool partagé. Bird réchauffe automatiquement une nouvelle IP dédiée sur environ 30 jours, avec le surplus acheminé via l'infrastructure partagée pendant la montée en charge. Consultez un spécialiste e-mail pour évaluer votre profil d'envoi avant de choisir.

Oui. Regroupez les IP en pools et routez chaque type de trafic vers son propre pool. Cela sépare les IP qui transportent vos flux de campagne et transactionnels. L'authentification, la réputation de domaine et l'engagement des destinataires restent importants pour les deux.

Bird handles SPF, DKIM, and DMARC authentication, dedicated IP pools with automated warmup, bounce and complaint suppressions, unsubscribe preferences, and real-time delivery analytics. You control list acquisition, message content, and sending cadence, and you can pair those controls with Inbox Insights to monitor inbox placement across providers.

Start in the dashboard or analytics API by breaking down bounce reasons and spam complaints by sending domain and mailbox provider, such as Gmail or Yahoo. You can inspect individual delivery attempts in the email log to see exact server responses, and use Inbox Insights to run seed tests or check whether providers are routing your mail to spam.

No. Health statuses like Healthy, Watching, and Throttled give you an early warning when bounce or complaint rates rise, without automatically pausing your traffic or changing your rate limits. Your team stays in control of whether to pause a broadcast or clean an audience while investigating.

When an address hard bounces, Bird adds it to your suppression list and blocks future sends to protect your sender reputation. Spam complaints and unsubscribes automatically stop future marketing emails to that recipient while allowing critical transactional messages, such as password resets or receipts, to reach valid addresses.

Les rebonds définitifs créent des suppressions pour tout le courrier ; les plaintes créent des suppressions pour le courrier non transactionnel. Les suppressions manuelles bloquent toutes les catégories. Les rebonds temporaires et les reports ne créent pas de suppressions permanentes de destinataires.

Une désinscription enregistre la préférence du destinataire dans l'onglet Préférences. Elle est distincte de la liste de suppressions. Les deux sont vérifiées au moment de décider s'il faut envoyer, et la suppression d'un contact n'efface pas sa désinscription.

Vous pouvez supprimer une suppression via le tableau de bord ou API après en avoir identifié la cause. La supprimer ne supprime pas les autres enregistrements de blocage ni les préférences de désinscription. L'adresse sandbox suppressed@messagebird.dev vous permet de tester un destinataire rejeté sans modifier votre liste.

Utilisez Email Lookup avec une clé API disposant du scope lookup. Soumettez une adresse et consultez son résultat, le niveau de confiance de délivrabilité, les indicateurs de risque et toute suggestion de correction de faute de frappe. Le tableau de bord, les SDKs et CLI permettent d'effectuer la même vérification.

Les résultats documentés sont valid, neutral, risky, undeliverable et typo. Traitez result comme un vocabulaire ouvert et gérez les valeurs futures à l'aide du niveau de confiance de livraison. Le booléen valid est l'évaluation de validité du fournisseur ; lisez-le en parallèle avec result et confidence, car il ne garantit pas la livraison.

Proposez la suggestion de correction à la personne pour qu'elle confirme ; ne remplacez jamais silencieusement son adresse. Neutral signifie que la boîte aux lettres n'a pu être confirmée dans aucun sens. Combinez le résultat et le niveau de confiance avec votre politique de consentement et d'envoi.

Non. Une vérification permet d'évaluer la qualité de l'adresse à un instant donné. Elle n'établit pas le consentement, ne supprime pas les préférences de désinscription et ne garantit pas le placement en boîte de réception. Continuez à respecter les enregistrements de suppression et de préférences.

Utilisez l'API de traitement par lots pour évaluer jusqu'à 1 000 adresses en une seule requête, dans la limite de 128 Kio par requête. Les résultats suivent l'ordre de soumission, doublons inclus. Chaque entrée traitée est facturée. Consultez les limites de rejeu documentées avant de réessayer un lot ; cette page ne fournit pas de contrôle d'import de liste.

You can track delivered messages, opens, clicks, bounces, spam complaints, and delivery latency. Filter and group performance by sending domain, recipient domain, mailbox provider, tag, template, or broadcast to spot trends quickly. You can also inspect delivery and bounce rates by sending IP to monitor infrastructure health.

Analytics update within minutes as delivery and engagement events arrive, and each report includes a freshness timestamp so you know how current the numbers are. Metrics are recorded when the event happens, meaning a link clicked on Tuesday appears in Tuesday's activity even if the email was sent earlier in the week. You can query hourly or daily rollups across the dashboard and reporting API.

Delivery metrics confirm that the recipient's mail server accepted your message. To see whether accepted emails land in the primary inbox or the spam folder across major providers, use Inbox Insights, and use Competitive Insights to benchmark competing brands. To measure revenue or signups, pass campaign tags or link parameters into your application's analytics.

No. You can generate a Bird forwarding address in seconds and forward emails from your existing inbox to start testing right away. When you are ready to receive mail directly on your own brand, you can configure a receiving subdomain.

Yes. Register and verify a dedicated subdomain in Bird, enable inbound receiving, and publish the provided MX records in your DNS. Using a dedicated subdomain lets Bird process application replies and support tickets while your primary domain continues routing employee mail to Google Workspace or Microsoft 365.

Bird sends a webhook notification to your server as soon as an incoming email arrives, and your app can fetch the parsed subject, plain text, HTML body, headers, and attachments through the API. You can verify webhook signatures to confirm each request came from Bird and rely on automatic retries if your endpoint is temporarily unavailable.

Inbound email turns incoming messages on your receiving domain or forwarding address into structured webhook events and parsed content for your backend. Agent Mailboxes give each AI agent or support workflow a dedicated inbox that tracks multi-turn conversation threads, filters unwanted senders, and sends replies in context.

Inbound email parses incoming messages and forwards them to your webhook endpoint for one-way processing. An agent mailbox gives your AI agent or support app a persistent inbox that groups messages into conversation threads, strips quoted reply history to keep prompts clean, enforces sender admission rules, and sends threaded replies.

Yes. You can create mailboxes on any verified domain or subdomain where you have enabled inbound receiving. For quick setup without DNS changes, you can also provision a generated or custom handle on Bird's managed inbox domain, which stays reserved to your workspace even if you delete the mailbox later.

Parsed message headers, clean extracted text, and attachments are stored for 30, 90, or 365 days based on the retention period you choose for your plan. Raw MIME files and unparsed original bodies are kept for 30 days so you can debug formatting or delivery issues.

Yes. Configure mailbox webhooks to trigger your agent automatically whenever an admitted message lands in the inbox, or connect to the live event stream for real-time updates during an active session. If a streaming connection drops, your agent can list recent thread messages through the API to catch up on anything that arrived while disconnected.

Inbox Insights is the current Bird dashboard experience for inbox placement and seed testing, replacing the older Inbox Tracker name. If your organization uses a standalone eDataSource or legacy Tracker account, you can continue signing in through that platform's existing portal and support team.

Your delivery rate shows how many emails were accepted by recipient mail servers, which includes messages that later get filtered into spam. Inbox Insights shows where those accepted messages actually land across major mailbox providers, breaking down primary inbox versus spam folder placement alongside your delivery metrics.

Verify your sending domain in a workspace with Inbox Insights enabled and turn on domain tracking. Once active, panel placement estimates populate for supported mailbox providers as your domain sends volume, and you can run seed tests using your plan's seed testing allowance.

No. Creating a seed test reserves a set of test addresses for you to include in your campaign audience or pre-send test list before the expiration date. Placement results populate in your dashboard as those seed mailboxes receive your email, and reserving a test uses one test from your allowance.

You can see inbox, spam, and missing counts for each measured mailbox provider, verify that SPF, DKIM, and DMARC passed on the received messages, and compare how engaged versus dormant test mailboxes filtered your campaign.

Inbox Insights is designed for interactive investigation in the Bird dashboard, where you can inspect placement trends and seed test results visually. For programmatic reporting on your sent volume, bounces, opens, and clicks, use the Email analytics API.

Yes. Competitive Insights is the Bird dashboard tool for tracking competing brands and benchmarking their email programs, replacing the older Competitive Tracker name. If your team uses a legacy standalone account, you can continue accessing it through its existing sign-in and support path.

Competitive Insights estimates volume and engagement from a representative panel of consumer mailboxes, tracking each watched brand's primary high-volume sending domain. Mail sent from secondary domains or very low-volume senders may not appear in the panel sample.

Yes. The campaign feed displays captured subject lines and rendered email screenshots when available from the panel. It focuses on observed broadcast campaigns to help you review messaging, cadence, and seasonal promotions across your industry.

Treat them as complementary signals. Competitor read rates come from observed mailbox activity in the measurement panel, whereas your own open rates come from tracking pixels in the emails you send. The dashboard labels panel estimates alongside your own delivery metrics so you can compare directional trends accurately.

Yes. Each brand profile lists the detected email service provider when the panel can identify it from message headers and sending infrastructure. If a sender's provider cannot be verified from observed mail, the field stays blank.

Open Competitive Insights in the Bird dashboard, search for competitors by brand name or sending domain, and add them to your watchlist up to your plan's brand allowance. You can also book a demo with our team to check panel coverage for your industry before you subscribe.

Both are self-managed mail transfer agents for organizations that run their own sending infrastructure. Momentum MTA is designed for carrier-grade, high-volume environments that need deep policy customization and routing control. PowerMTA gives enterprise senders high-throughput delivery and granular queue management on their own hardware or public cloud instances in AWS, Azure, or GCP.

Momentum MTA and PowerMTA fit enterprises and mailbox providers whose compliance or infrastructure policies require running dedicated mail servers on-premises or in their own cloud. Inbox Insights and Competitive Insights are cloud tools in the Bird dashboard for any sender who wants inbox placement testing and competitor benchmarking, and you can use both without self-hosting an MTA.

SparkPost fait partie de Bird. Bird Email fournit les workflows d'envoi, de campagne et de délivrabilité pour les nouveaux projets. Une intégration SparkPost existante est une intégration distincte : examinez ses appels API, ses enregistrements de domaine et ses événements avec votre équipe de compte avant de planifier une migration.

Bird Email possède ses propres API et SDKs. Consultez les guides d'envoi, de modèles, de domaine et de webhooks plutôt que de supposer qu'une requête SparkPost peut être envoyée telle quelle.

Momentum est notre plateforme d'infrastructure e-mail on-premise pour l'envoi à haut volume, avec des workflows personnalisables, un routage et des paramètres de livraison configurés via son Policy Manager. Il est conçu pour évoluer avec votre volume d'envoi tout en maintenant des performances stables, et il prend en charge l'Unicode complet (SMTPUTF8) pour envoyer vers des jeux de caractères internationaux.

Adaptive Delivery est le façonnage automatique du trafic de Momentum. Il observe comment chaque fournisseur de messagerie réagit à vos e-mails et s'ajuste en temps réel : limitation, report ou pause temporaire d'un flux pour protéger votre réputation, puis montée en charge une fois la situation rétablie. Vous atteignez la boîte de réception sans surveiller manuellement les débits d'envoi pour chaque fournisseur. L'Intelligence Router vous montre ces ajustements en temps réel sur toutes vos sources de données, avec des alertes à chaque modification.

Oui aux deux. Momentum fonctionne sur vos propres serveurs, sur n'importe quel cloud majeur, ou en combinant les deux, afin de s'adapter à votre infrastructure, vos coûts et vos exigences de conformité — et vous pouvez faire évoluer cette répartition au fil du temps. Il continue aussi d'évoluer : les versions récentes le maintiennent à jour avec les systèmes d'exploitation modernes, TLS 1.3, et les standards de sécurité et SMTP actuels, et exposent les événements de messages via des API en temps réel que vous pouvez intégrer à vos propres outils de reporting et d'automatisation.

Oui. PowerMTA peut relayer une partie du trafic vers l'API Bird Email hébergée tout en livrant le reste directement depuis vos propres serveurs — c'est le moyen le plus simple de tester la plateforme hébergée ou de migrer progressivement sans tout déplacer d'un coup. PowerMTA lui-même fonctionne sur une infrastructure que vous possédez, donc ces IP restent sous votre gestion. Le trafic relayé vers la plateforme hébergée peut utiliser nos IP ou vos propres IP dédiées, tandis que tout le reste reste entièrement sous votre contrôle.

Les MTA virtuels vous permettent d'exploiter plusieurs flux d'envoi indépendants au sein d'une même instance PowerMTA, chacun avec ses propres IP, sa réputation et ses limites. Utilisez-les pour gérer séparément le courrier transactionnel, le courrier marketing ou différents clients. Les domaines partagés et les politiques des fournisseurs de destinataires peuvent tout de même affecter la délivrabilité entre les flux.

Yes. API requests require HTTPS, and SMTP submission requires TLS encryption on port 465 or a completed STARTTLS upgrade on ports 587 and 2525 before authentication is accepted, keeping your credentials encrypted in transit. Unencrypted submission on port 25 is disabled. To keep data in your chosen region, send through the regional endpoint that matches your API key; Bird's official SDKs and CLI detect the key's region prefix and route requests automatically.

You choose the exact read or write permissions for each API key across email sending, marketing campaigns, and domain management, so a key created for an application server to send receipts cannot modify your domains or access unrelated resources. Administrative actions such as managing team members, workspace settings, API keys, and IP pools require an authenticated user session. You can also attach an IP address allowlist to any key so requests from unfamiliar networks are rejected.

When you rotate an API key, Bird issues a replacement key immediately and keeps the previous key active for a configurable grace period (24 hours by default) so you can roll out the new credential across your services without dropping traffic. If a key is compromised, you can set the grace period to zero to revoke it right away, and you can assign a custom expiration date to the new key if your security policy requires periodic rotation.

Yes. Bird supports enterprise single sign-on over SAML 2.0 and OIDC with identity providers such as Okta, Microsoft Entra ID, and Google Workspace. Your account team can enable SSO for your organization, and team members who sign in with an email and password can enable multi-factor authentication on their own accounts.

Yes. The organization audit log records configuration and administrative changes in a read-only timeline showing the actor, workspace, timestamp, and outcome, and you can export entries in OCSF format to your SIEM. The audit log tracks account and infrastructure actions, while individual sent and received emails are recorded in the email log.

You can download compliance certifications and security documentation from the Bird Trust Center at trust.bird.com, and review our data processing agreement, privacy statement, and acceptable use policy at bird.com/legal. If your procurement or security team requires a custom vendor questionnaire, contact your account team.