Silent Network Authentication verifies that the device making the request owns the phone number,
without sending an SMS code. It is available when the organization has SNA enabled and the flow's
Phone module has snaVerification set in GET /omni/onboarding/flow.
Phone number resolution. Send phoneNumber to verify the number the user just typed. When the
body is empty or absent, the number is resolved from the session in this order: the phone already
stored on the session, the phone/phoneNumber custom field, the most recent PHONE form answer,
the OAuth loginHint. The resolved number is stored on the session and echoed back in
phoneNumber, with phoneSource telling where it came from. A client can therefore call this
endpoint before showing the phone capture screen and skip the screen when the response carries a
phoneNumber (success: true, or success: false with fallbackReason). A response with
errorCode carries no phone number: show the capture screen on PHONE_REQUIRED, and handle the
other codes as errors.
Outcomes. The endpoint always answers HTTP 200; branch on the body:
success: true- SNA started. OpencheckUrlfrom the device over its mobile data connection (not Wi-Fi), capture thecodereturned by the redirect and send it toPOST /omni/sna/complete.success: falsewithfallbackReason- SNA is not possible for this number (organization or flow has SNA disabled, network not covered, SIM swapped in the last 7 days, provider error). The number is still saved on the session. Continue with SMS OTP:GET /omni/send/otpthenGET /omni/compare/otp?code={code}(both accept the same LIMITED token and default to SMS).success: falsewitherrorCode- the request itself failed, seeerrorCode.