Bird review

Bird is a hosted communications API paired with a SaaS dashboard. It sits between an application and the delivery channels—email, SMS, WhatsApp, Apple Messages and voice—so an engineering team can integrate messaging without building a separate provider connection for every channel. The dashboard adds operational tools for templates, event-driven workflows, contact audiences, analytics and workspace controls.

Applications can send messages through Bird and respond to delivery events. The vendor describes email endpoints, signed webhooks, idempotent retries and a sandbox for simulating deliveries, bounces and spam complaints. The dashboard also supports WhatsApp template drafts, voice call flows and email conversations. This makes Bird more than a transport API: it combines messaging interfaces with tools for configuring and monitoring campaigns and workflows. Bird is presented as a hosted service; the available product details do not describe a self-hosted server or an embeddable messaging library.

Bird’s homepage presents a REST API alongside SDKs for Node.js, Python, Go and PHP. It also lists a CLI, MCP and serverless as ways to build and check delivery from code, a terminal or an AI assistant. The email example uses POST /v1/email/messages; the page shows an accepted response followed by a delivery event. Confirm endpoint coverage and SDK support for each channel in Bird’s developer docs before choosing an integration surface.

The vendor describes webhooks for delivery, bounce and spam events, signed webhook verification, and retries of timed-out requests without duplicate sends. Its sandbox can simulate email deliveries, bounces and spam complaints. Error messages are intended to identify rejected requests. In the dashboard, developers and operators can create WhatsApp templates, trigger workflows from application events, configure voice sequences and reply to customer email. These features offer both API and interface-based configuration; teams should decide which settings belong in code and which belong in workspace operations.

Bird has free and paid email sending plans, but the published pricing summary does not give free sending limits. Email uses monthly wallet funding from $15. Other channels are largely usage-based: US outbound long-code SMS is listed at $0.0035 per segment, and US WhatsApp marketing messages at $0.005 each. SMS carrier fees and WhatsApp Meta fees are separate. Voice is charged per minute, with rates varying by destination and duration.

Some adjacent services have fixed listed prices: US local phone numbers cost $0.50 per month, and dedicated IPs cost $24.95 per IP per month, with possible setup fees. Lookup is $0.005 per answered phone lookup. Verify has no separate verification fee, but channel messages are charged. Automations charge per workflow invocation; message charges are separate. Inbox software is free, but channel usage still costs money. Usage draws from the Bird balance, and unused balance carries forward. Annual billing is not shown. Ask Bird for channel-specific limits and a volume estimate before forecasting production costs.

Bird is presented as a hosted API and dashboard. Bird does not publish an open-source licence or a self-hosting option in the product details, so teams should plan around a vendor-hosted service unless Bird confirms otherwise. That means the application depends on Bird’s API and the delivery channels it exposes, rather than on a server the team can operate itself.

The available product details do not describe data export or migration tooling. Ask Bird how to export contacts, templates, message history, delivery events and workflow definitions, and whether exports are available in machine-readable formats. REST and webhook integration provide familiar boundaries for application code, but they do not make stored configuration or historical data portable by themselves. Before committing, document which components are managed in code, how credentials and message records can be retrieved, and what happens to numbers and channel registrations during a provider migration.

Bird describes several production-oriented controls: a sandbox for simulated email outcomes, signed webhooks, delivery events and idempotent retries for timed-out requests. Its analytics cover delivery rates, bounces, carrier failures and voice call outcomes. These are useful integration points, but the vendor’s published product details do not state API rate limits, throughput ceilings, availability targets or retention periods. Ask for those figures and any channel-specific restrictions before sizing a deployment.

Budget separately for channel usage and fees: SMS carrier charges and WhatsApp Meta fees are additional, while voice rates vary by destination and duration. Wallet funding applies to some products, and phone-number rental and dedicated-IP setup may add charges. The published details do not set out security certifications, data residency, a service-level agreement or support response times; confirm each with Bird for your requirements. Test webhook verification, retry behavior and failure handling in your own application, and establish monitoring for delivery events and balance consumption.