Skip to main content
POST
Check Membership Credentials
Validates a member’s password against their stored credentials, enabling password-based login within your loyalty portal. The password must be hashed (bcrypt or MD5 depending on your program configuration) before sending — never transmit plaintext passwords. On success, the response includes the member’s internal Id and basic profile details. For OTP-based login, use Generate OTP by Relation ReferenceVerify OTP by Relation Reference instead.

Responses

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

Example:

"jane.doe@example.com"

ProgramId
integer
required

Your loyalty program ID

Example:

19

RelationType
integer
required

Use 4 for customers

Example:

4

Password
string
required

Member's password hashed using bcrypt or MD5 as configured for your program.

Example:

"$2b$10$hashed_password_here"

Response

Credentials valid — returns member profile

results
object