Update a native contact
Changes the fields you name and leaves the rest alone.
An empty string clears a custom field, which is also the only way to make a “field is set” trigger able to fire again. A field key that does not exist on this sub-account is an error, not a silent drop.
Changing phone re-checks the do-not-call history for the new number, on the same rule as a create: correcting a typo onto a number that asked not to be called brings that decision with it.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: contacts:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
The contact id.
1Query Parameters
The sub-account. It is the only thing that identifies the tenant on these routes, and it is re-checked against your access on every call. A sub-account that keeps its contacts in a CRM answers 400.
Body
The fields to change.
Only the fields you name are changed. An empty string clears one.
"+13125550142"
100100254200200200200Response
The contact as it now is.
