Changelog · back to all

WhatsApp is now a Verify channel

feature

You can now deliver one-time passcodes over WhatsApp, alongside SMS and email. WhatsApp OTPs are sent from the shared Bird Authifly sender — the same "Authifly" brand you already see on our shared email sender — using the built-in authentication template, so there's no template or sender setup required. Support for your own dedicated senders is following shortly.

What's new

  • Enable WhatsApp per country from the Verify → Countries settings in the dashboard.
  • Automatic failover: if the primary channel can't deliver, Verify falls back through your configured channels before giving up.
  • API & SDK: whatsapp is now a valid value for a verification's channel, and country routes accept a whatsapp key in their per-channel settings. This is additive — no breaking change.

Default routing change

Existing phone verifications now default to SMS → WhatsApp → email: SMS stays primary, with WhatsApp as an automatic fallback before email. Countries you've already customized are left untouched.

Start with one channel.
Add the others when you're ready.

A test API key is yours immediately. Production unlocks when you add a payment method and verify a sender.

Get startedRead docs

Using Claude Code, Cursor, or Codex? Copy a setup prompt and your agent installs the Bird CLI and skills for you. Pick yours:

Cursor