Recently shipped.

Bird Verify is now available to every workspace. Send a one-time passcode and confirm the code your user enters in two API calls — no sender to register, and no verification id to store.

Getting started

• Verify your first customer
• Verify overview
• Sending verifications

What's available

• Send and check: start a verification with POST /v1/verify/verifications — which also resends after the cooldown — then confirm the code with the check endpoint. A code can be checked once.
• Email and SMS with failover: pick the channels and their order; if the first channel can't deliver, Verify falls back to the next one on the same code budget.
• Per-country configuration: set channel availability and order, per-country senders, and a verified-domain email sender — a per-workspace overlay on Bird's per-country base.
• Built-in safety: code length and lifetime, maximum attempts, resend cooldown, and per-recipient and per-workspace rate limits, all configurable.
• Everywhere you build: the Verify API, the dashboard (onboarding, verifications log, countries, and configuration), the bird verify CLI, the Bird MCP server, and the Go, TypeScript, and Python SDKs.

More is on the way — WhatsApp and voice channels, dedicated senders, and customer-authored templates among them.

The WhatsApp Metrics page is out of "coming soon" and live in the dashboard at WhatsApp → Metrics. It's the aggregate view of your channel that the per-message message log can't give you: delivery rate and failure rate measured against fixed thresholds (95% and 5%), accepted volume, and cost, over the last 24 hours, 7, 30, or 90 days.

Below the summary tiles:

• A delivery-over-time chart of accepted, delivered, and failed volume, to spot spikes and bad sends.
• A failure-rate trend line plus a histogram of failures by Bird-normalized error code.
• Delivery latency, Bird's own processing time from accepting a message to handing it to the WhatsApp network, at p50/p95/p99.
• Breakdowns by sending number, template category, and tag, each with its own Healthy/Watching/Throttled status.

Alongside it, WhatsApp's rate limits now have their own reference page: a dedicated whatsapp_send group (10/min base) for sending, kept separate from the shared list/read/write management limits so send quota is never eaten by management traffic.

Bird launches a headless signup path for agents that don't already have a Bird account. Three commands take an agent from nothing to a stored, working credential: bird auth signup creates the account and emails a six-digit code, bird auth verify-email confirms it and returns a one-time onboarding ticket, and bird auth create-org consumes that ticket to create the first organization and workspace. No browser and no dashboard involved at any step. The same flow is exposed as the signup, verify_email, and create_org tools on the MCP server. See Self-serve signup.

Also in this release:

• The dashboard's navigation is redesigned around a left sidebar: channels are grouped under Products (Voice, Push, Lookup, and Realtime now sit in a coming-soon row), shared records live under Resources (Contacts, Numbers, Verification), and API Keys, Webhooks, and Logs are pinned at the bottom and stay visible no matter which channel you're in. See the dashboard tour.
• WhatsApp message endpoints (get, list, list message events, send) now return last_error.meta_error_code, the raw error code from the WhatsApp Cloud API, for lower-level debugging of failed sends.
• Corrected docs: enabling email receiving on a domain is dashboard-only, through the Receiving toggle on the domain's detail page. The previously documented PATCH /v1/email/domains/{domain_id} call for this doesn't do that. Separately, the 422 error returned for preview email fields (references, attachment path, contact_id, topic_id) used ahead of general availability is UnsupportedEmailFeature, not unsupported_feature as previously documented.

SMS sending is now available to every Bird workspace. Send a message in seconds and follow it all the way to delivery, on whichever surface you build on.

Getting started

• SMS overview
• Sending SMS

What's available

• Free-form text SMS: send your own message text with an alphanumeric sender, gated by per-country policy and your workspace's enabled destination countries.
• Send by template: send a ready-made Bird SMS template by name, with your own variables.
• Delivery tracking: get a message, list your messages, and follow each message's delivery timeline — or receive sms.* webhooks as status changes.
• Everywhere you build: the SMS API, the dashboard (message log, send, templates, metrics, and destination settings), the bird sms CLI, and the Go, TypeScript, and Python SDKs.

More is on the way — customer-authored templates and additional languages among them.

The WhatsApp messaging API brings tags and metadata in line with the rest of the platform. When you send a WhatsApp message, you can now attach:

• Tags: structured {name, value} labels, up to 20 per send, for low-cardinality dimensions like category or experiment_variant
• Metadata: an arbitrary JSON object (up to 2 KB) for your own per-send context, such as internal IDs

Both are echoed back on the message resource and on list results, which also gain a tag query parameter to filter by tag name or an exact name:value pair, matching the filtering already available for email and SMS messages.