Update Contact (PATCH)
Updates a contact. Identical to the documented PUT on the same path — Rails routes both verbs to the same action, so use whichever your client prefers.
custom_attributes is merged, not replaced: keys you send are added or overwritten and keys you leave out stay. Use the destroy-custom-attributes endpoint to remove one.
Authorizations
This token can be obtained by visiting the profile page or via rails console. Provides access to endpoints based on the user permissions levels. This token can be saved by an external system when user is created via API, to perform activities on behalf of the user.
Path Parameters
ID of the contact
Body
name of the contact
"Alice"
email of the contact
"alice@acme.inc"
whether the contact is blocked or not
false
phone number of the contact
"+123456789"
Send the form data with the avatar image binary or use the avatar_url
The url to a jpeg, png file for the contact avatar
"https://example.com/avatar.png"
A unique identifier for the contact in external system
"1234567890"
An object where you can store additional attributes for contact. example {"type":"customer", "age":30}
An object where you can store custom attributes for contact. example {"type":"customer", "age":30}, this should have a valid custom attribute definition.
Response
Success
Most single-contact responses wrap the contact in a payload key. Create is the exception — it nests it further, under payload.contact.