Verify v1 API has reached End of Sale. It is now closed to new customers and will be fully deprecated in the future.
For new development, we encourage you to use the Verify v2 API. v2 has an improved developer experience and new features, including:
- Twilio helper libraries in multiple languages
- PSD2 Secure Customer Authentication Support
- Improved Visibility and Insights
Existing customers will not be impacted at this time until Verify v1 API has reached End of Life. For more information about migration, see Migrating from 1.x to 2.x.
HTTP Status Codes
||Response is correct. The body of the response will include the data requested.|
||There was an error with the request. The body of the response will have more info.|
||API usage limit. If you reach API usage limits, a 429 will be returned. Please wait until you pass the limit and attempt the call again.|
||There are multiple possible reasons for a
|60201||Invalid verification code|
|60202||Max check attempts reached|
|60203||Max send attempts reached|
|60204||Service does not support this feature|
|60205||SMS is not supported by landline phone number|
|60206||'Amount' & 'Payee' params are required|
|60207||Max rate limits per service reached|
|60208||Rate limit with that UniqueName already exists|
|60209||UniqueName format is invalid|
|60210||Max Buckets per Rate limit reached|
|60211||Bucket with the given Interval already exists|
|60212||Too many concurrent requests for phone number|
|60213||A Messaging Configuration already exists for the given country|
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.