Update a customer

put

https://{project_url}/webservice/rest-api/{api_interface}/{version}/customers/{customer_id}

Update the information on a specific customer account.

Replaces the customer's personal information, contact details, address, consent records, and optional property records with the values provided in the request body. The customer password is changed only if a new password is provided; omitting the password field leaves it unchanged.

To update multiple custom property records in bulk without affecting other customer data, use POST /customers/{customer_id}/properties/batch.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

customer_id

string

required

The unique ID of the customer.

Body Params

customer

object

required

Basic information about a customer.

password

This is the customer’s password. The parameter does not follow the usual PUT request rules. If you do not include it, the password will not change.

social_network_credentials

object

This is the customer’s social media credentials.
Special Rule for PUT Request with social network credentials: Unlike typical HTTP PUT requests, the request will not erase existing data if parameters are missing. If you do not include the social media credentials in the PUT request, the existing credentials will remain unchanged.

property_records

array of objects

length ≤ 1000

List of customer property records. Only properties with standard data types (string, integer, boolean, float, date, timestamp, enum, multiselect) can be set. If a dynamic or system property is included, the API returns HTTP 400 with reason code not_allowed_value. See the Properties section for details.

property_records

Headers

Accept-Language

string

Defaults to cs, en-gb;q=0.8

The unique ID of the language code by ISO 639-1.

Responses

204

No Content

`error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.

429

Too many requests - more than the resource limit.

503

Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

Language

Credentials

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

401The client has invalid credentials or auth token.

403The client does not exist or the client tried to access an unauthorized property or resource.

404The request path does not match any API route, or the addressed resource does not exist.

405The request path matches a valid route, but the endpoint does not support the HTTP method used in the request.

500Server is not working as expected.