Skip to main content
There are two kinds of errors in the SNA flow:
  1. Request & authentication errors — returned as an HTTP 4xx with a top-level errorCode when a Create or Status Check request is rejected (invalid parameters, bad credentials, etc.).
  2. SNA verification errorsSP-prefixed codes returned by the verification engine. They appear inside auths[].error (with errorCode, message, and a user-friendly description) on the Status Check API when the PRIMARY factor’s status is FAILED.

Request & authentication errors

Returned as an HTTP 4xx with a top-level errorCode by the Create (POST /auth/v1/create) and Status Check (GET /auth/v2/status) APIs. Both APIs share these codes; the Applies to column notes any that are specific to one endpoint.

SNA verification errors

When the PRIMARY factor’s status is FAILED, the Status Check API returns an error object in auths[].error containing the errorCode, a short message, and a user-friendly description. Surface the description to end users; use the errorCode to drive fallback or retry logic.

Verification & operator errors

Returned when carrier verification could not complete. Operator/eligibility checks (SP40004SP40008) are rejected up front; the remaining codes are reported once verification has been attempted.

SDK-reported errors

Reported by the client SDK when the silent network handshake fails on the device (timeouts, connectivity, or operator-URL issues).

System errors