Update Person

Description

This method allows for updating the profile of a currently logged-in consumer.

---

Request

Restrictions

This service requires an authenticated user and can only be called after a successful consumer login.

Endpoint

PUT https://<server-url>/api/v4/person

Parameters

Parameter	Location	Description
touchpoint	Query / Header	The identifier for the touchpoint making the request. If sent as a header, the name must be Thalamus-Touchpoint.
token	Query / Header	The authentication token for the API session. If sent as a header, the name must be Thalamus-Token.
activity	Query / Header	Optional. The activity to be used. If sent as a header, the name must be Thalamus-Activity.
Content-Type	Header	Specifies the content type of the request body. Must be application/json.

Full URL Example

https://<server-url>/api/v4/person?touchpoint=test&token=testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttest

Request Body

The request body contains the updated information for the consumer's profile, consumer data, and opt-in settings.

Field	Type	Description
consumers	Array	An array containing consumer-specific data like brand preferences and consumption frequency.
profile	Object	An object containing the consumer's personal information. For a full list of available fields, see the Get Profile Fields document.
optIns	Array	An array used to manage the consumer's communication opt-in and opt-out preferences for various channels and brand families.

JSON

{
  "consumers": [
    {
      "activeConsumer": true,
      "consumptionFrecuency": 7,
      "preferedBrandId": 1,
      "alternativeBrandId": 5,
      "competitiveMarketId": 3
    }
  ],
  "profile": {
    "birthday": 1353380400000,
    "phone": {
      "number": "47965555",
      "areaCode": "12",
      "type": "cellphone",
      "intCode": "53"
    },
    "email": "[email protected]",
    "address": {
      "countryId": 1,
      "street2": "",
      "street1": "Catulo Castillo 6666",
      "postalCode": "5601",
      "stateId": 1,
      "type": "home",
      "city": "Buenos Aires"
    },
    "lastname": "Johnnn",
    "gender": "Female",
    "firstname": "Malkovichhhh",
    "arg_party_reference": [
      "[email protected]"
    ],
    "policy_agreement": true,
    "digital_data_agreement": true
  },
  "optIns": [
    {
      "brandFamilyId": 1,
      "channel": 6001,
      "accepted": false
    }
  ]
}

---

Response

✅ Successful Response: 200 OK

The consumer's profile has been successfully updated. The response returns the updated session context.

JSON

{
  "context": {
    "links": [
      {
        "ref": "home",
        "href": "http://localhost:8080/thalamus/api/v1/people/home"
      },
      {
        "ref": "profile",
        "href": "http://localhost:8080/thalamus/api/v1/people/profile"
      },
      {
        "ref": "consumer",
        "href": "http://localhost:8080/thalamus/api/v1/people/consumer"
      }
    ],
    "activities": [
      {
        "links": [],
        "code": "EMileage",
        "name": "E Mileage",
        "message": "E Mileage. You can accumulate points ...",
        "type": "GENERIC"
      }
    ],
    "simpleProfile": {
      "firstName": "Malkovich",
      "lastName": "John",
      "email": "[email protected]"
    }
  }
}

❌ Unsuccessful Response: 400 Bad Request

Returned if the provided data is invalid. For a detailed list of possible validation errors, please refer to the Unsuccessful Response section of the Person Registration method.