Two-factor authentication.
Confirm sensitive account actions with an extra one-time code.
Your account
Confirm it’s you.
Enter the code sent to
+1 ••• ••• 6620
Your account
Confirm it’s you.
Enter the code sent to
+1 ••• ••• 4567
Verify logins and step-up actions without managing OTP state.
Building two-factor authentication in-house usually means maintaining database tables for hashed codes, expiry windows, resend cooldowns, and failed-attempt counters. With the Bird Verify API, your app sends a code when a user signs in, resets a password, or approves a payout, then checks the submitted code directly against their phone number or email address. Your session store keeps no verification IDs between steps, and the same flow supports passwordless login when the code itself is the credential.
How Bird keeps two-factor sign-ins fast and secure.
Reliable delivery across channels with built-in protection against code guessing and traffic pumping.
01Trigger on password check, confirm on code entry.
Request a code as soon as the user's password passes or they start a sensitive action like a payout or email change, then verify the digits they submit. Calling the send endpoint again for a delayed code resends cleanly on the active verification without invalidating a code that is already on the way.02Reach users on SMS, WhatsApp, voice, or email.
Prevent user lockouts when carrier filtering delays an SMS or a traveler has no cellular signal. Deliver codes to a phone number over SMS, WhatsApp, or a spoken voice call, or send passcodes to an email address using your existing contact details.03Update channel routing and expiry rules without a deploy.
Configure country-specific channel order, code length, and expiration windows once in your workspace across sign-ins, password resets, and step-up checks. When a customer reports a failed login, per-verification delivery logs show which channel ran and whether the code was delivered, mistyped, or expired.04Block brute-force guessing and SMS pumping.
Enforce attempt limits that invalidate a code after repeated wrong guesses, alongside per-recipient send caps that stop attackers or bots from draining your messaging budget through repeated resend requests.
Add a second factor to your sign-in handler.
Send a verification code after validating the user's password, and check the digits when they submit the second-factor form. The check response tells your app whether the code matched, how many attempts remain on a typo, or whether the window expired so you can prompt the user clearly.
// Send the second factor once the password checks out.
await bird.verify.verifications.create({
to: { phone_number: user.phone },
}).safe();
const { data, error } = await bird.verify.verifications.check({
to: { phone_number: user.phone },
code: submitted,
}).safe();
if (error) throw error;
if (data.success) grantSession(user);
Build it on the Verify platform
Channels, fallback routing, and abuse controls for your authentication flows.
- SMS OTPDeliver one-time codes over local and international carrier routes with registered sender IDs.
- Email OTPVerify logins and sensitive actions through the user's inbox when they sign up with an email address or lack mobile coverage.
- Channel orchestrationSwitch delayed verifications between SMS, WhatsApp, voice, and email using country-specific routing rules.
- Anti-abuse & code securityProtect sign-in flows against brute-force guessing and SMS pumping with hashed codes, attempt limits, and send caps.
- Verify API overviewExplore the complete platform for two-factor authentication, passwordless sign-in, and signup verification across channels.
Scale without losing control.
Separate production and sandbox traffic into dedicated workspaces, scope API keys to the exact channels each service or agent needs, and track permission changes in the audit log.