Skip to main content
This page covers the SNA-only integration of the OTPless Headless SDK in React Native. The SDK accepts the requestId generated by the Create API, performs the silent network handshake, and reports progress through callbacks. Your backend confirms the final result via the Status Check API.

​
Requirements

RequirementVersion
React Native0.64+
Android Minimum SDK21
iOS13.0+

​
Step 1: Add SDK dependency

Install the OTPLESS Headless SDK at the root of your React Native project: 
npm i otpless-headless-rn
For iOS, install the pods: 
cd ios && pod install
Check the latest version of the SDK on npm.

​
Step 2: Smart Authentication (SNA) setup

Make sure Silent Network Authentication is enabled on the OTPLESS dashboard. For an SNA-only configuration, SNA must be the only channel enabled.
Add the network security config inside android/app/src/main/AndroidManifest.xml, in your <application> tag:
AndroidManifest.xml
android:networkSecurityConfig="@xml/otpless_network_security_config"

​
Step 3: Initialize the SDK

Create a OtplessHeadlessModule instance, initialize it with your App ID, and register the response callback: 
import { OtplessHeadlessModule } from 'otpless-headless-rn';

const headlessModule = new OtplessHeadlessModule();

useEffect(() => {
    headlessModule.initialize("YOUR_APP_ID");
    headlessModule.setResponseCallback(onHeadlessResponse);
    return () => {
        headlessModule.clearListener();
        headlessModule.cleanup();
    };
}, []);
Replace YOUR_APP_ID with your actual App ID from the OTPLESS dashboard.

​
Step 4: Start SNA with the requestId

Pass the requestId returned by the Create API to start(): 
const headlessRequest = {
    requestId: "REQUEST_ID_FROM_API"
};

headlessModule.start(headlessRequest);
Start polling the Status Check API from your backend immediately after calling start(). The SDK callback and the server status run in parallel.

​
Step 5: Handle callbacks

const onHeadlessResponse = (response: any) => {
    headlessModule.commitResponse(response);

    switch (response.responseType) {
        case "SDK_READY": {
            // SDK initialized successfully — enable your continue button
            // or proceed with user authentication.
            break;
        }
        case "FAILED": {
            // SDK initialization failed
            if (response.statusCode === 5003) {
                // Please try to initialize the SDK again.
            }
            break;
        }
        case "INITIATE": {
            // Authentication has been initiated
            if (response.statusCode !== 200) {
                handleInitiateError(response);
            } else if (response.response?.authType === "SILENT_AUTH") {
                // SNA is being attempted — show a loading state.
            }
            break;
        }
        case "VERIFY": {
            // Verification failed for the attempted authType.
            if (response.response?.authType === "SILENT_AUTH" && response.statusCode === 9106) {
                // SNA verification failed — treated as AUTH_TERMINATED.
            }
            break;
        }
        case "ONETAP": {
            // Final success response — returns token / idToken
            break;
        }
        case "AUTH_TERMINATED": {
            // SNA-only configuration: auth could not complete.
            // Emitted when pre-checks fail, or when SNA was attempted
            // and then failed. Treat as a terminal failure and rely on
            // the Status Check API for the exact error.
            break;
        }
    }
};

​
Callback reference

The SDK works in two steps — initialization and start() — and each step has its own set of callbacks.

​
Step 1: Initialization callbacks

Emitted when you initialize the SDK (Step 3).
CallbackMeaning
SDK_READYSDK initialization completed.
FAILEDSDK failed to initialize (e.g. statusCode 5003).

​
Step 2: Start callbacks

Emitted after you invoke start() (Step 4).
CallbackStateMeaning
INITIATENon-terminalSNA is being attempted after pre-checks pass. authType is SILENT_AUTH.
VERIFYNon-terminalVerification failed for the attempted authType (e.g. statusCode 9106 for SILENT_AUTH).
ONETAPSuccess — terminalSNA completed successfully (Silent Mobile Verification). Returns token / idToken.
AUTH_TERMINATEDFailed — terminalEmitted in two cases: (1) pre-checks failed → terminated directly; (2) SNA was initiated and then failed.
In the SNA-only configuration AUTH_TERMINATED is a terminal failure with no fallback. Always treat the Status Check API result as authoritative. See Handling the AUTH_TERMINATED callback.
For the errorCode / statusCode values surfaced in SDK callbacks, see SDK Error Codes.

​
Next step

Status Check API

Confirm the authoritative auth status from your server.