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

Best Practices for Verify SNA Error Handling


Test SNA Today

Skip the 2-4 week wait for carrier approvals and get directly to testing SNA with your own mobile number using the new Live Test Number feature.

Get Started

You can check for errors by calling the Verification Check API and inspecting the response property sna_attempts_error_codes. Silent Network Auth (SNA) specific error codes always begin with 605xx.

In general, you can failover to SMS or another Verification channel for all error codes. The exception to this is error code 60540, which indicates that the phone number is invalid and an SMS Verification would also fail. We don't recommend writing specific handling logic for each error code beyond falling back to another Verification channel because error codes may be added or changed over time.


Client error codes received after SNA URL invocation

client-error-codes-received-after-sna-url-invocation page anchor

Besides 605xx error codes, there are also client error codes. After the SNA URL is received from a Start New Verification API call, it must be invoked from the client with a GET or POST request. You will receive an HTTP 200 OK as a response (assuming no other issues) and a client error code value.

Example:

A browser with text ErrorCode=0&ErrorDescription=Success&Carrier=VZW.Rate this page:

Need some help?

Terms of service

Copyright © 2024 Twilio Inc.