Auth + Device Fingerprint
Validates an OTPless auth token and returns the device fingerprint in one backend-to-backend call. Requires clientId and clientSecret.
- Read
deviceFingerprinting.status(SUCCESS,FAILED,PENDING,TIMEOUT) before using the data. PENDINGandTIMEOUToccur only in ASYNC mode.- A
FAILEDfingerprint does not mean auth failed; the top-levelstatusis stillSUCCESS.
Integration flows
Both modes call this same endpoint. The difference is only in when the SDK returns the auth token to your app.ASYNC mode
Authentication and device fingerprinting run concurrently. The SDK returns the auth token as soon as authentication completes, without waiting for fingerprinting to finish. The fingerprint result is attached by the OTPless backend when your backend calls validate token.SYNC mode
The SDK returns the auth token only after both authentication and device fingerprinting have completed. This guarantees fingerprint data is always available when your backend calls validate token.PENDING and TIMEOUT can only occur in ASYNC mode, where the SDK returns the auth token before fingerprinting completes. In SYNC mode, the SDK waits for fingerprinting to finish, so the status is always SUCCESS or FAILED.Authorizations
The clientId used for API authentication.
The clientSecret used for API authentication.
Body
Payload containing the auth token received from the OTPless SDK.
The auth token received from the OTPless SDK.
Response
Authentication completed. Check deviceFingerprinting.status for the fingerprint result.
The auth token passed in the request.
SUCCESS when authentication passed.
"SUCCESS"
Unique user identifier assigned by OTPless.
ISO 8601 timestamp of the authentication event.
Device fingerprint result. Present when Device Fingerprinting is enabled.