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.

从一个渠道开始。
准备好后,再添加其他渠道。

测试 API 密钥即刻可用。添加支付方式并验证发送者身份后,即可解锁生产环境。

正在使用 Claude Code、Cursor 或 Codex?复制一条设置提示,您的智能代理即可自动安装 Bird CLI 和相关技能。选择您的工具:

Cursor