Skip to main content
POST
/
lbms-ingress
/
member
/
api
/
Member
/
VerifyOTPByRelationReference
Verify OTP by Relation Reference
curl --request POST \
  --url https://loyalife-api.xoxoday.in/lbms-ingress/member/api/Member/VerifyOTPByRelationReference \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "UniquerefID": "jane.doe@example.com",
  "OTP": 123456,
  "DestinationAddress": "192.168.1.1",
  "Destination": "Web",
  "OtpType": "LOGIN",
  "ProgramId": 19,
  "RelationType": 4
}
'
{
  "results": {
    "IsSucessful": true,
    "ErrorCode": "000",
    "ExceptionMessage": "Success",
    "ReturnObject": true
  }
}

Documentation Index

Fetch the complete documentation index at: https://help-loyalife.xoxoday.com/llms.txt

Use this file to discover all available pages before exploring further.

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

PathTypeDescription
results.IsSucessfulbooleantrue
results.ErrorCodestring000
results.ExceptionMessagestringSuccess
results.ReturnObjectbooleantrue on successful verification

Authorizations

​
Authorization
string
header
required

JWT obtained from Generate Auth Token. Pass as Authorization: bearer {token}.

Body

application/json
​
UniquerefID
string
required

The member's RelationReference (CID)

Example:

"jane.doe@example.com"

​
OTP
integer
required
Example:

123456

​
DestinationAddress
string
required
Example:

"192.168.1.1"

​
Destination
enum<string>
required
Available options:
Web,
Mobile
Example:

"Web"

​
OtpType
enum<string>
required

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"

​
ProgramId
integer
required
Example:

19

​
RelationType
integer
required
Example:

4

Response

200 - application/json

OTP verified