Create Profile
Member Management
Create Profile
Browse the complete reference for all 19 Loyalife API endpoints across 4 modules.
POST
Create Profile
Registers a new member in your loyalty program. The
relation_reference you supply becomes the member’s permanent identifier across all Loyalife APIs — choose it carefully (typically an email-based UUID or your internal customer ID). New members are created in Inactive status by default; activation happens through a separate workflow. If a member with the same relation_reference already exists, the API returns a 409 rather than overwriting.
Member Status Values
Status can be managed both via API and through the Loyalife Admin portal. Any mandatory custom attributes defined in your CPD schema must also be included in the request. Optional custom attributes can also be passed.
Responses
200 — Success
200 — Success
409 — Member Already Exists
409 — Member Already Exists
Error Codes
email_id is configured as non-mandatory for some programs (e.g. Citibank). Mandatory field codes E103–E107 only fire when the field is configured as required for your program.Authorizations
JWT obtained from Generate Auth Token. Pass as Authorization: bearer {token}.
Query Parameters
Your loyalty program ID
Example:
19
Body
application/json
Unique member identifier — typically email-based. Primary key across all APIs.
Example:
"jane.doe@example.com"
Example:
"Jane Doe"
Example:
"jane.doe@example.com"
Example:
"+919876543210"
Use 5 for Inactive — standard initial state for new enrollments.
Example:
"5"
Example:
"123 Main Street, Mumbai 400001"
Available options:
M, F, O Example:
"F"
Date of birth in YYYY-MM-DD format
Example:
"1990-06-15"
Response
Member created