Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Error Codes


(warning)

Warning

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

http-status-codes page anchor
StatusReason
200 OKResponse is correct. The body of the response will include the data requested.
400 Bad RequestThere was an error with the request. The body of the response will have more info.
429 Too Many RequestsAPI 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.
503 Service UnavailableThere are multiple possible reasons for a HTTP 503 error.

StatusError Message
60200Invalid parameter
60201Invalid verification code
60202Max check attempts reached
60203Max send attempts reached
60204Service does not support this feature
60205SMS is not supported by landline phone number
60206'Amount' & 'Payee' params are required
60207Max rate limits per service reached
60208Rate limit with that UniqueName already exists
60209UniqueName format is invalid
60210Max Buckets per Rate limit reached
60211Bucket with the given Interval already exists
60212Too many concurrent requests for phone number
60213A Messaging Configuration already exists for the given country

Rate this page: