Verify OTP by Relation Reference
OTP
Verify OTP by Relation Reference
Validate a LOGIN OTP using the member’s RelationReference.
POST
Verify OTP by Relation Reference
Completes the OTP verification for a member identified by their
RelationReference. This is the second and final step of the CID-based OTP flow — call this after Generate OTP by Relation Reference has dispatched the code. The OtpType must match exactly what was used in the generate call; a mismatch will result in a failed verification even if the numeric code is correct.
OTP expiry duration and maximum attempt limits are configurable at the program level in Loyalife Admin — confirm these values with your Xoxoday implementation contact.
Responses
200 — Success
200 — Success
| Path | Type | Description |
|---|---|---|
results.IsSucessful | boolean | true |
results.ErrorCode | string | 000 |
results.ExceptionMessage | string | Success |
results.ReturnObject | boolean | true on successful verification |
Authorizations
JWT obtained from Generate Auth Token. Pass as Authorization: bearer {token}.
Body
application/json
The member's RelationReference (CID)
Example:
"jane.doe@example.com"
Example:
123456
Example:
"192.168.1.1"
Available options:
Web, Mobile Example:
"Web"
Purpose of the OTP. Must match between Generate and Verify calls.
Available options:
ACTIVATION, LOGIN, FORGOTPWD, CHANGEPASSWORD, RESETPASSWORD, FORGOTUSERNAME, TwoFA, UNBLOCKMEMBER, NONE, CASHBACKCONFIRM, POINTTRANSFERCONFIRM, FAMILYPOOLINGMERGE, FAMILYPOOLINGUNMERGE, AIRREVIEWNCONFIRM, DOMESTICFLIGHTREVIEWNCONFIRM, HOTELREVIEWNCONFIRM, CARREVIEWNCONFIRM, GIFTCARDREVIEWNCONFIRM, PACKAGEREVIEWNCONFIRM, SHOPREVIEWNCONFIRM, SHOPDIGITALREVIEWNCONFIRM, MERCHANTREVIEWNCONFIRM, ISPREVIEWNCONFIRM, INSURANCEREVIEWNCONFIRM Example:
"LOGIN"
Example:
19
Example:
4
Response
200 - application/json
OTP verified