Changelog — Bird

What’s new. What’s next for you.

Product releases and developer updates from Bird.

Available numbers show which business-address area applies

Get and list available numbers can now return ownership_address_area_name (for example Amsterdam) for a local number whose ownership_address_scope is number_area, meaning its ownership paperwork needs a business address inside the number's own area. The field names the area when it is known and is omitted otherwise. The buying numbers guide also now states that a number carrying ownership_address_scope is removed if its paperwork isn't approved by the registration deadline, with any setup fee credited back but its first recurring charge not refunded.

Also in this release:

Pick conversation labels from one workspace list

Labels on conversations now come from one list per workspace, shared by email mailboxes, Apple Messages for Business and WhatsApp in the dashboard. Open a conversation's labels to search the workspace's list, apply a label, or create a new one from what you typed.

Auth0: guided setup for Bird as your phone provider

A guided integration for Auth0 is now available. It walks through using Bird as Auth0's Custom Phone Provider, with screenshots of each step in Auth0 and Bird and the provider code to paste.

Auth0 generates and checks each sign-in code, and Bird Verify delivers it by SMS or voice call for MFA, and by SMS for passwordless login. If your tenant also sends account notifications, such as blocked-account, password-change and password-breach messages, they go out through Bird SMS with the text from your Auth0 templates. Setup needs a Bird API key stored as an Auth0 secret, plus an SMS sender for account notifications, and no OAuth client.

Set up Auth0 with Bird.

Verify: send your verification codes in your own email template

Verify can now send the one-time passcode in an email you designed. Build the email in Email Templates, publish it, and choose it as the body of your custom email sender. Your users get your layout, wording, and languages; Verify keeps checking codes, attempts, and expiry exactly as before. The guide Your own verification email walks through the setup, with the rules the template must meet and how to troubleshoot a refused save.

Get started

What's new

Send WhatsApp templates with named parameters and dynamic bindings

Sending most WhatsApp templates no longer requires building the components array by hand. POST /v1/whatsapp/messages now accepts a template.parameters object keyed by each variable's name (or position, for a numbered placeholder), plus fixed keys for a media header, a location header, a button URL suffix, or an authentication code. The template version's variables array lists the keys the template takes and which are required, so you can build the object from the API response instead of guessing.

A template language can also define parameter bindings: Liquid that computes a value from the parameters you send, set with PUT a template language. A binding can read a recipient's contact record, which isn't possible for a single send, so a language with contact-reading bindings returns 422 on create-whatsapp-message and instead resolves per recipient in a broadcast. A template with parameter bindings, or with named variables in a carousel card or a button URL, accepts only parameters; sending it with components is rejected. See Components and parameters for the full key reference.

Also in this release: