Sélection d'API email
Choose the right email API for your workload
Deliver transactional emails, run marketing campaigns, and manage AI agent mailboxes from one platform. Ship and operate email workflows through the REST API, SDKs, CLI, and Bird MCP.
This shortlist matches each provider to the workload it fits best and spells out the trade-offs before you integrate. Every pricing table compares published rates side by side and separates a spendable Bird balance from fixed monthly send allowances.
Trusted by engineering and product teams
shipping at global scale.
Quel API email convient à votre application ?
Choose Bird when you want transactional delivery, marketing broadcasts, and conversational agent inboxes in a single account. Use the table below to see where other providers fit specific workloads. These recommendations reflect documented product capabilities rather than inbox-placement rankings.
| Fournisseur | À choisir pour | À vérifier avant de choisir |
|---|---|---|
| Bird | Transactional email, marketing campaigns, and agent mailboxes in one workspace, complete with reusable templates, audience targeting, threaded replies, and inbound sender rules. | Plan how you will map message streams and suppressions when migrating an existing app, since Bird’s message category tags traffic rather than isolating infrastructure. Review the idempotent retry window and single-address email lookup guide. |
| Resend | React Email templates rendered and sent directly from the Node SDK. | Dedicated IPs require the Scale plan and an add-on, while managed IP pools scale dynamically without exposing the underlying IP addresses. |
| Postmark | Message Streams that keep transactional receipts and broadcast traffic on separate IP ranges. | Safe send retries require your own deduplication logic: Postmark does not support request idempotency keys and recommends combining status-code checks with delivery webhooks. |
| Mailgun | Inbound Routes that filter incoming emails and forward or store matching messages. | Mailgun’s Inbox Placement test key prevents duplicate seed tests rather than deduplicating customer email retries. |
| Amazon SES | Applications already running on AWS that manage email sending, verified identities, configuration sets, and suppression lists through IAM and the AWS CLI. | AWS pricing bills send volume, account tiers, attachment data transfer, and optional add-ons separately instead of bundling a monthly send allowance. |
| SendGrid | Subusers that isolate sending domains, analytics, team permissions, and credit limits under a parent account. | Inbound Parse posts incoming mail and attachments to your webhook URL, leaving thread state and message storage up to your application. |
| MailerSend | Hosted MCP tools and a CLI for sending email and SMS and managing domains, templates, and recipients. | Dedicated IPs are gated by monthly sending volume and manual review on qualifying plans. |
| Brevo | MCP tools for managing CRM contacts, marketing campaigns, templates, and domains. | Batch retry protection covers the entire multi-version batch request at once and expires after 30 minutes. |
Comment Bird, AgentMail et Nylas se comparent-ils pour l'état des boîtes mail ?
All three products provision hosted inboxes that store incoming messages and track reply threads for software and AI agents. The Nylas column covers Agent Accounts, which give an autonomous agent its own mailbox without OAuth access to an employee inbox.
| Exigence de boîte mail | Bird | AgentMail et Nylas Agent Accounts |
|---|---|---|
| Webhook analysé | The inbound mail webhook delivers mailbox, thread, and message identifiers alongside sender details, recipients, and quote-stripped reply text with a flag when long bodies are truncated. | AgentMail: Inbound mail events include message and thread payloads, though plain-text and HTML availability depends on what the sender transmitted. Nylas: Inbound notifications announce newly stored mail, and large payloads omit the body so your app fetches the full message via the API. |
| Contenu stocké | Stored mailbox messages retain headers, extracted reply text, and attachments so agents can read context on demand, while full bodies and inbound raw MIME follow configurable retention windows. | AgentMail: Message retrieval returns stored content and reply text stripped of quoted history, with separate calls for raw MIME and attachments. Nylas: Agent Account mailboxes organize stored messages in folders under policy-defined storage and retention limits. |
| Provisionnement d'adresse | Provision a mailbox in one call on a generated address for instant testing, or bind it to your own receiving-enabled custom domain. | AgentMail: Create an inbox on the default domain or a verified custom domain, with optional auto-generated usernames. Nylas: Provision a hosted Agent Account via the API or CLI without user OAuth on either a custom domain or a Nylas trial domain. |
| État des fils et des réponses | Conversation threads track participants and unread counts automatically: replying appends to the existing thread while composing starts a new conversation. | AgentMail: Reply actions keep outbound responses inside the same retrievable thread. Nylas: Threaded replies set standard reply headers automatically and attach the sent message to the active Agent Account thread. |
| Règles d'expéditeur | Receive policies and sender rules restrict an inbox to existing threads or approved senders. Blocked messages stay inspectable in a separate folder without triggering webhooks or agent runs, or can be dropped outright. | AgentMail: Allow and block lists filter outbound sends, new inbound mail, and replies at the organization, pod, or inbox level. Nylas: Workspace rules govern inbound and outbound mail separately and reject blocked senders during the SMTP handshake before storage. |
| Opérations d'agent | CLI commands and MCP tools let agents create mailboxes, read conversation threads, and send replies, while mailbox management APIs configure receive policies and sender allowlists. | AgentMail: Hosted MCP tools create inboxes, read threads, send messages, and reply. Nylas: Agent Account CLI and API workflows provision accounts, send mail, and read replies using an account grant identifier. |
Quel est l'avantage de Bird ?
Bird pairs its own MTA and IP-reputation network with campaign management and programmable agent inboxes. Engineering and growth teams work from the same REST API, SDKs, CLI, and MCP tools rather than stitching together separate transactional, marketing, and inbound vendors.
| Capacité | Avantage de Bird | Ce qu'il faut évaluer |
|---|---|---|
| Héritage en délivrabilité | Bird acquired SparkPost in 2021, and its sending network delivers roughly 40% of the world’s commercial email. | Bird’s Momentum MTA adapts throughput per mailbox provider in real time, while dedicated IPs and pools automate IP warm-up with shared-pool overflow. |
| Outillage d'agent | Bird’s hosted MCP server lets AI agents send email and manage domains, templates, and inboxes directly, while the Bird CLI and typed SDKs bring the same operations to terminals and application code. | Test the exact operations your automation or coding agent will run, including error recovery. Bird’s CLI outputs structured JSON and semantic exit codes so scripts and agents can branch reliably. |
| Boîtes aux lettres | Bird’s agent mailboxes give support workflows and AI agents dedicated email addresses, grouped conversation threads, quote-stripped replies, and sender filtering. | Decide whether your app only needs a stateless inbound webhook or a persistent inbox that tracks threads, stores messages, and blocks unwanted senders before waking your agent. |
Pour quel usage chaque fournisseur est-il adapté ?
Weigh each provider’s core strength against the operational work it leaves to your team. Every head-to-head guide below compares the sending stack, agent tooling, inbound handling, migration steps, and published pricing.
Bird
E-mail transactionnel, campagnes et boîtes de réception agents. Bird runs its own global sending infrastructure for transactional receipts and audience-targeted marketing broadcasts, and also licenses PowerMTA for on-premises delivery. Programmable agent mailboxes handle inbound threads, replies, and sender rules in the same workspace. When migrating, map your current provider’s stream separation and suppression lists into Bird.
SendGrid
Sous-utilisateurs et workflows d'envoi établis SendGrid subusers partition sending reputation, permissions, and credit caps across business units, and its CLI supports basic terminal sends. Because Inbound Parse forwards raw parsed email to your webhook without storing threads, inventory your inbound webhook handlers before migrating.
Amazon SES
E-mail au sein d'une application AWS The AWS CLI and AWS MCP Server let teams manage identities, configuration sets, and sends using existing IAM roles and SigV4 authentication. SES receiving rules drop incoming mail into S3 buckets or SNS topics, leaving parsing, storage, and reply threading to your own AWS services.
Mailgun
Routage des messages entrants Mailgun Routes match incoming mail against header or recipient expressions and trigger forwarding or temporary storage. Its open-source MCP server exposes sending, domain, route, template, and deliverability tools, though you host and run the server process yourself.
Postmark
Séparation transactionnel et broadcast Postmark Message Streams keep transactional mail and broadcast traffic on separate IP pools by default. Postmark provides an open-source MCP server and CLI for templates and delivery inspection, while its inbound webhook posts parsed JSON to your app without hosted mailbox state.
MailerSend
Opérations e-mail via CLI et MCP MailerSend’s hosted MCP server and CLI cover email and SMS sending alongside domain, template, webhook, and suppression management. When migrating, keep temporary On Hold soft-bounce suppressions separate so 72-hour holds do not become permanent blocks.
Brevo
Opérations contacts et campagnes Brevo’s MCP server connects AI tools to CRM contacts, campaigns, templates, and domains, while its CLI focuses on OAuth app setup and local testing. Note that batch retry deduplication applies to the entire batch payload for 30 minutes.
Resend
Modèles React et réception Resend’s Node SDK renders React Email components directly on send, and its receiving API exposes inbound content, attachments, and reply headers. Resend also offers a hosted MCP server and CLI for sending and domain management.
Comment se comparent les offres e-mail publiées ?
Expand any provider below to compare Bird’s live rates against that vendor’s published plans at matching monthly volumes. Pay attention to how billing works: a Bird funding deposit stays in your workspace as spendable balance across channels, whereas a bundled tier charges a flat fee for a fixed monthly email cap. Each competitor figure links to its pricing page with the date it was verified.
Bird / Amazon SES
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Not comparable. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| Palier Bird | Volume inclus des forfaits payants | Bird | Amazon SES |
|---|---|---|---|
| Free | 1,000 | Forfaits 4 à ce volumeDéveloppez pour comparer chaque option et ses conditions de facturation. Volume correspondant À la carte outbound email: $0.10 / 1,000 emails 1,000 emails No monthly fee; uncapped usage rate, not a monthly allowance; attachment data charged separately. tel que publié Volume correspondant Essentials: $0.16 per 1,000 emails 1,000 emails Usage rate for the 0–10M emails/month band, not a monthly allowance. No account fee; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page. tel que publié Volume correspondant Pro: $0.22 per 1,000 emails 1,000 emails Usage rate for the 0–10M emails/month band, not a monthly allowance. $105 per account per region per month; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page. tel que publié Volume correspondant Enterprise: $0.23 per 1,000 emails 1,000 emails Usage rate for the 0–10M emails/month band, not a monthly allowance. $500 per account per region per month; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page. tel que publié | |
| Email Startup | Aucun sur les forfaits payants | €15 / month to shared balance (EUR); email usage charged separately $15 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
| Email Growth | Aucun sur les forfaits payants | €250 / month to shared balance (EUR); email usage charged separately $250 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
| Email Scale 1,000 | Aucun sur les forfaits payants | €1,000 / month to shared balance (EUR); email usage charged separately $1,000 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
| Email Scale 2,500 | Aucun sur les forfaits payants | €2,500 / month to shared balance (EUR); email usage charged separately $2,500 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
| Email Scale 5,000 | Aucun sur les forfaits payants | €5,000 / month to shared balance (EUR); email usage charged separately $5,000 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
| Email Scale 10,000 | Aucun sur les forfaits payants | €10,000 / month to shared balance (EUR); email usage charged separately $10,000 / month to shared balance (USD); email usage charged separately | Voir les forfaits publiés ci-dessous |
Amazon SES: Forfaits publiés
1,000 emails
No monthly fee; uncapped usage rate, not a monthly allowance; attachment data charged separately.
tel que publié
1,000 emails
Usage rate for the 0–10M emails/month band, not a monthly allowance. No account fee; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page.
tel que publié
1,000 emails
Usage rate for the 0–10M emails/month band, not a monthly allowance. $105 per account per region per month; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page.
tel que publié
1,000 emails
Usage rate for the 0–10M emails/month band, not a monthly allowance. $500 per account per region per month; attachment data charged separately. Tiered rates apply marginally; higher-volume rates are on the publisher page.
tel que publié
Bird / Brevo
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Mixed by volume. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| E-mails par mois | Forfait Bird et trésorerie mensuelle requise | Brevo |
|---|---|---|
| 5,000 | Email Startup: €15 (EUR) | |
| 50,000 | Email Startup: €18.000000000000004 (EUR) | |
| 100,000 | Email Startup: €36.00000000000001 (EUR) | |
| 250,000 | Email Startup: €90.00000000000001 (EUR) | |
| 500,000 | Email Startup: €180.00000000000003 (EUR) | |
| 150,000 | Email Startup: €54.00000000000001 (EUR) | |
| 1,000,000 | Email Startup: €360.00000000000006 (EUR) | Professional: €999.00/month 1,000,000 emails Monthly billing; optional add-ons excluded. tel que publié |
| 3,000,000 | Email Scale 1,000: €1,000 (EUR) | Professional: €1,713.00/month 3,000,000 emails Monthly billing; optional add-ons excluded. tel que publié |
Brevo: Forfaits publiés
1,000,000 emails
Monthly billing; optional add-ons excluded.
tel que publié
3,000,000 emails
Monthly billing; optional add-ons excluded.
tel que publié
Bird / MailerSend
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Mixed by volume. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| E-mails par mois | Forfait Bird et trésorerie mensuelle requise | MailerSend |
|---|---|---|
| 500 | Free: $0 (USD) | |
| 5,000 | Email Startup: $15 (USD) | |
| 50,000 | Email Startup: $20 (USD) | |
| 100,000 | Email Startup: $40 (USD) | |
| 250,000 | Email Startup: $100 (USD) | |
| 500,000 | Email Startup: $200 (USD) | |
| 1,000,000 | Email Startup: $400 (USD) | |
| 2,000,000 | Email Startup: $800 (USD) |
MailerSend: Forfaits publiés
Bird / Mailgun
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Bird. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| E-mails par mois | Forfait Bird et trésorerie mensuelle requise | Mailgun |
|---|---|---|
| 50,000 | Email Startup: $20 (USD) | |
| 100,000 | Email Startup: $40 (USD) | |
| 250,000 | Email Startup: $100 (USD) | |
| 500,000 | Email Startup: $200 (USD) | |
| 1,000,000 | Email Startup: $400 (USD) | |
| 2,500,000 | Email Startup: $1,000 (USD) |
Mailgun: Forfaits publiés
Bird / Postmark
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Mixed by volume. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| E-mails par mois | Forfait Bird et trésorerie mensuelle requise | Postmark |
|---|---|---|
| 100 | Free: $0 (USD) | |
| 10,000 | Email Startup: $15 (USD) | |
| 50,000 | Email Startup: $20 (USD) | |
| 125,000 | Email Startup: $50 (USD) | Basic: $115.00/mo 125,000 emails Monthly billing; volume covers emails sent and received. tel que publié |
| 300,000 | Email Startup: $120 (USD) | Basic: $245.00/mo 300,000 emails Monthly billing; volume covers emails sent and received. tel que publié |
| 700,000 | Email Startup: $280 (USD) | Basic: $455.00/mo 700,000 emails Monthly billing; volume covers emails sent and received. tel que publié |
| 1,500,000 | Email Startup: $600 (USD) | Basic: $775.00/mo 1,500,000 emails Monthly billing; volume covers emails sent and received. tel que publié |
Postmark: Forfaits publiés
125,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
300,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
700,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
1,500,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
1,500,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
10,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
50,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
125,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
300,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
700,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
1,500,000 emails
Monthly billing; volume covers emails sent and received.
tel que publié
Bird / Resend
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Mixed by volume. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
| E-mails par mois | Forfait Bird et trésorerie mensuelle requise | Resend |
|---|---|---|
| 3,000 | Email Startup: $15 (USD) | |
| 50,000 | Email Startup: $20 (USD) | |
| 100,000 | Email Startup: $40 (USD) | |
| 200,000 | Email Startup: $80 (USD) | |
| 500,000 | Email Startup: $200 (USD) | |
| 1,000,000 | Email Startup: $400 (USD) | |
| 2,500,000 | Email Startup: $1,000 (USD) |
Resend: Forfaits publiés
Bird / SendGrid
Les forfaits payants de Bird ajoutent un dépôt mensuel à un solde partagé. Les envois transactionnels sont facturés au tarif du forfait. La comparaison ci-dessous suppose que le solde sert uniquement à l'email ; les autres usages et les options sont facturés en supplément.
Verdict tarifaire: Not comparable. Pour chaque volume inclus chez un concurrent, le besoin de trésorerie mensuel estimé de Bird correspond au plus élevé entre le dépôt du forfait payant et l'usage transactionnel à son tarif publié. Le forfait Free utilise son volume inclus lorsqu'il est disponible. Les dépôts constituent un solde utilisable, pas des frais supplémentaires. Seuls les volumes et devises correspondants dont les tarifs sont complets influent sur le verdict.
SendGrid: Forfaits publiés
50,000 emails
Monthly billing; published volume range is 50,000 to 100,000 emails. Taxes and overages may apply.
tel que publié
100,000 emails
Monthly billing; published volume range is 100,000 to 2,500,000 emails. Taxes and overages may apply.
tel que publié
Comment choisir un API e-mail ?
Comment Bird compare-t-il les fournisseurs d'API e-mail ?
Comment comparer les coûts des API d’e-mail ?
Comment tester une API e-mail avant de changer de fournisseur ?
Comment migrer vers l'API e-mail de Bird ?
Mettez-le en pratique.
Poursuivez avec la documentation, les guides et les exemples sur ce sujet.
Poursuivre la lecture
Commencez par le workflow, puis planifiez la migration.
Contactez notre équipe e-mail
Testez la compatibilité avec votre programme e-mail.
Comparez le flux d'envoi, les contrôles de délivrabilité et les plans publiés avec vos exigences. Puis testez l'intégration ou planifiez une migration avec notre équipe.
Créez votre compte et testez votre intégration avant de décider comment transférer votre trafic de production.