Update Customer
PATCH
/v1/customers/complytId/{complytId}Patch Customer by Complyt Id
Request
Customer complytId
The unique identifier in Complyt of the customer
the attribute designed to receive a unique identifier provided by API consumers themselves (e.g. pass your own ID)
a single digit which identifies your different stores, checkout solutions, marketplaces, etc. defined by the API consumers (to avoid external id duplications)
The customer's name
An (Optional) Email address associated with the customer
Indicates whether the customer is 'retail'/'reseller'/'marketplace'
read-only. The APIs internal timestamps for this resource
valid ISO8601 format. Supported formats are 'YYYY-MM-DD'/ 'YYYY-MM-DDTHH:mm:ssZ'/ and 'YYYY-MM-DDTHH:mm:ss±hh:mm' (with a valid time zone offset).
valid ISO8601 format. Supported formats are 'YYYY-MM-DD'/ 'YYYY-MM-DDTHH:mm:ssZ'/ and 'YYYY-MM-DDTHH:mm:ss±hh:mm' (with a valid time zone offset).
External timestamps, which should reference the dates in your originating system since these are the timestamps used for sales tax calculation
The creation time of the transaction
The last update time of the transaction
{
"name": "NameToPatch",
"address": {
"city": "Sacramento",
"country": "US",
"county": null,
"state": "CA",
"street": "10010 Patched St.",
"zip": "95823"
}
}
Request samples
Responses
The unique identifier in Complyt of the customer
the attribute designed to receive a unique identifier provided by API consumers themselves (e.g. pass your own ID)
a single digit which identifies your different stores, checkout solutions, marketplaces, etc. defined by the API consumers (to avoid external id duplications)
The customer's name
An (Optional) Email address associated with the customer
Indicates whether the customer is 'retail'/'reseller'/'marketplace'
read-only. The APIs internal timestamps for this resource
valid ISO8601 format. Supported formats are 'YYYY-MM-DD'/ 'YYYY-MM-DDTHH:mm:ssZ'/ and 'YYYY-MM-DDTHH:mm:ss±hh:mm' (with a valid time zone offset).
valid ISO8601 format. Supported formats are 'YYYY-MM-DD'/ 'YYYY-MM-DDTHH:mm:ssZ'/ and 'YYYY-MM-DDTHH:mm:ss±hh:mm' (with a valid time zone offset).
External timestamps, which should reference the dates in your originating system since these are the timestamps used for sales tax calculation
The creation time of the transaction
The last update time of the transaction
{
"complytId": "9f8ee193-1a71-42b4-801d-ee1d8a161fbe",
"externalId": "externalIdExample",
"source": "sourceExample",
"name": "NameToPatch",
"address": {
"city": "Sacramento",
"country": "US",
"county": null,
"state": "CA",
"street": "10010 Patched St.",
"zip": "95823"
"isPartial": false
},
"email": "example@some.mail.com",
"customerType": "RETAIL",
"internalTimestamps": {
"createdDate": "2023-01-10T17:40:44.357",
"updatedDate": "2023-01-11T17:10:21.275"
},
"externalTimestamps": {
"createdDate": "2022-10-19T07:00:00",
"updatedDate": "2022-10-19T09:07:54.585"
},
"comment": "this is a customer"
}