Skip to main content
POST
/
lbms-ingress
/
member
/
api
/
Member
/
UpdateProfileWithAttributes
Update Profile
curl --request POST \
  --url https://loyalife-api.xoxoday.in/lbms-ingress/member/api/Member/UpdateProfileWithAttributes \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": 12345,
  "data": {
    "full_name": "Jane Smith",
    "mobile_number": "+919876543211"
  }
}
'
{
  "results": {
    "IsSucessful": true,
    "ErrorCode": "000",
    "ExceptionMessage": "Success",
    "ReturnObject": true
  }
}
Updates one or more profile fields for an existing member. Only the fields you include in the data object are changed — omitted fields are left unchanged. The internal id (not RelationReference) is required as the update key; obtain it from Get Member Profile first. Custom attributes defined in your CPD schema can be updated the same way as standard fields.
At least one data.* field must be present. Custom attributes from your CPD schema can also be included under data. Member status (Active, Suspended, etc.) can be managed via the Loyalife Admin portal or via API — see Create Profile for the full status code reference.

​
Responses

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

​
Error Codes

CodeExceptionMessageCause
000SuccessProfile updated successfully
E202Member nonexistentMember with the provided internal id does not exist
E204Record updation failed — cancelled memberCannot update a cancelled member
E205Duplicate Email: The email already existsUpdated email_id already belongs to another member
E206Duplicate Mobile: The mobile number already existsUpdated mobile_number already belongs to another member
103Member does not existMember not found in the program
104Failed to update member profileUpdate operation failed
113Member is cancelledMember account has been cancelled
999Bad requestMalformed payload or missing internal member id

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
​
id
integer
required

Internal member ID from the Id field in Get Member Profile response.

Example:

12345

​
data
object

Profile fields to update. At least one attribute required.

Response

200 - application/json

Profile updated