What we do
Tools
Industries
Department
How we workLet's talk →
Home/Twilio/Twilio Verification API
Twilio Verify

The Twilio Verification API: Two Calls, What Each Code Costs, and Keeping Fraud Off the Bill

Twilio Verify sends a one-time code and tells you whether the code someone typed back is right. You don't generate, store or expire codes yourself. The API is two requests; most of the work is deciding when to ask and what an approval should change in your app.

The two calls

Send a code: POST to verify.twilio.com/v2/Services/{ServiceSid}/Verifications with To (the phone number or email) and Channel (sms, call, email or whatsapp).

Create a Verify Service Start a verification Check the code

Check it: POST to .../VerificationCheck with To and Code. The status comes back approved if it matches and stays pending if it doesn't.

After that: an approved or expired verification is deleted (expiry is 10 minutes), so checking it again returns a 404.

Other methods such as TOTP authenticator apps, Push, passkeys and Silent Network Auth are part of Verify too, each with its own API.

What a month of sign-up codes costs

Verify charges a base fee only for verifications that succeed, plus the channel's own cost for each message sent. Failed, expired and abandoned ones skip the base fee, but their texts still cost.

Example month · 1,000 sign-ups by US SMS · Twilio list rates
Texts sent (1,000 first codes plus 100 resends) 1,100
SMS channel fee at $0.0083 each $9.13
Verifications approved (150 never finished) 850
Base fee at $0.05 per approved $42.50
Month total $51.63

Rates are Twilio's published US figures and change by country and channel. The number that wrecks this estimate is SMS pumping: thousands of codes sent to numbers nobody owns. That's what Fraud Guard is for.

Where Verify integrations go wrong

The check returns 404

How you'll know: A user enters the right code and your app gets a not-found error.

Fix: The verification was already approved, expired after 10 minutes, or hit its attempt limit, and Twilio deleted it. Start a new verification and tell the user a fresh code is on its way. The Verify logs in the Console show which of the three happened.

An SMS bill that jumped overnight

How you'll know: Thousands of verifications to one country you don't sell in, almost none approved.

Fix: That's SMS pumping. Turn on Fraud Guard in the Verify Service's SMS settings (Basic, Standard or Max; Standard is the default level) and switch off countries you don't serve in Geo Permissions. Blocked sends show as error 60410.

A wrong code treated as a failure

How you'll know: Users who mistype once get kicked back to the start.

Fix: A wrong code leaves the status pending, not failed. Let them try again against the same verification until it's approved or the attempts run out.

Approved, and nothing happens

How you'll know: Verify says approved, but the account stays locked or the booking unconfirmed until staff step in.

Fix: Verify only knows the code matched. Your app has to mark the phone verified, open the account or confirm the booking in the same request that receives the approval.

Verify, or codes sent through the regular SMS API?

Twilio Verify

Codes handled for you

  • Code creation, expiry and checking built in. Nothing to store.
  • SMS, voice, email and WhatsApp from one API.
  • Fraud Guard against SMS pumping, included in the base fee.
  • Paid per successful verification plus channel fees.
Programmable Messaging

Codes you build yourself

  • You generate, hash, store and expire every code.
  • You write the attempt limits, resend rules and fraud checks.
  • You pay only for the messages, with no per-verification fee.
  • US texting needs the sender registration covered on our Twilio API page.

For login and sign-up codes, Verify is usually the better deal: the base fee costs less than the code-handling and fraud work you'd otherwise maintain.

The decisions Verify leaves to your app

Verify confirms that whoever holds a phone or inbox right now could read the code. It doesn't know if that number belongs to an existing customer, a brand-new signup, or someone trying to take over an account. That logic belongs in your own system.

The useful questions are about when to ask. Every login, or only a new device? Before a payout change, a large booking, a password reset? And what an approval opens: a verified flag on the user, a released order, a confirmed appointment written back to the system that holds it.

n-frames builds that layer around Verify: the rules that decide when a code is needed, the write-back that acts on approved results in your user or booking records, and Fraud Guard and country settings tuned to where your customers really are. For flows that ask for a code inside a phone menu or text conversation, see Twilio Studio.

Questions people ask

What is Twilio Verify, and how is it different from sending an SMS?

Twilio's API for one-time verification. You ask it to send a code by SMS, voice call, email or WhatsApp, then ask it whether the code the user typed is right. It's used for two-factor login, confirming a phone number at sign-up, and checking identity before a sensitive change.

Can Twilio Verify send codes by voice call instead of text?

Yes. Set the channel to call and Twilio reads the code aloud. It's the usual fallback for landlines or users who never get the text.

Does Twilio Verify stop fraud or spam on its own?

Partly. Fraud Guard blocks SMS pumping by watching for unusual traffic and blocking suspect destination prefixes, and Geo Permissions let you switch off countries. It covers SMS only, and it won't spot suspicious sign-up patterns in your own app. Those checks are built around Verify.

How is Twilio Verify different from just sending a code through the regular SMS API?

With the regular SMS API you create, store, expire and check the code yourself and write your own fraud limits. Verify does that for you and charges a base fee per successful verification on top of the message cost.

How much does the Twilio Verify API cost?

A base fee per successful verification ($0.05 at Twilio's published rate) plus the channel cost, such as the US SMS rate. Failed, expired and unfinished verifications don't pay the base fee, though their messages may still be charged.

What does Twilio error 60410 mean?

Fraud Guard blocked the SMS because the destination looked like SMS pumping. If it's blocking real customers in a country you serve, review the protection level or adjust Geo Permissions for that country.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.