Skip to main content
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


Error Codes

email_id is configured as non-mandatory for some programs (e.g. Citibank). Mandatory field codes E103E107 only fire when the field is configured as required for your program.

Authorizations

Authorization
string
header
required

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

Query Parameters

pintProgramId
integer
required

Your loyalty program ID

Example:

19

Body

application/json
relation_reference
string
required

Unique member identifier — typically email-based. Primary key across all APIs.

Example:

"jane.doe@example.com"

full_name
string
required
Example:

"Jane Doe"

email_id
string<email>
required
Example:

"jane.doe@example.com"

mobile_number
string
required
Example:

"+919876543210"

status
string
required

Use 5 for Inactive — standard initial state for new enrollments.

Example:

"5"

address
string
Example:

"123 Main Street, Mumbai 400001"

gender
enum<string>
Available options:
M,
F,
O
Example:

"F"

dob
string<date>

Date of birth in YYYY-MM-DD format

Example:

"1990-06-15"

Response

Member created