Update a client
Update mutable fields on a client (the end customer of the partner) for the partner the API key belongs to. Only the fields you include in the request body are modified; omitted fields are left as-is. A supplied emails or phoneNumbers array replaces that whole branch, while an omitted one is left unchanged. customProperties accepts the custom properties defined for your partner, keyed by property id; send null to clear one. Requires the client:write scope.
Authorizations
Send the API key in the x-api-key header.
Path Parameters
^ovcid-.*$"ovcid-22222222-2222-4222-8222-222222222222"
Body
1"Sam"
1"Client"
Custom property values, keyed by property id. Ids and value types come from the properties defined for your partner, so this object cannot be described field by field here: an unknown id or a value that does not match the property type is rejected with 400. Only the ids you send are modified — omit a property to leave it untouched. To clear one, send null; a blank string and an empty array count as empty too, for every property type alike.
Response
Updated client
^ovcid-.*$Custom property values, keyed by property id. Ids and value types come from the properties defined for your partner, so this object cannot be described field by field here — call the custom-property list endpoint to resolve an id to its name and type. A property never given a value takes the default configured for it, and is left out rather than returned as null when there is no default either. A value stored before its property was changed — an option renamed or removed, the type switched — is returned as stored, so it may not match the type the property has today; an absent key is the only reliable sign that nothing is set.