List contacts

Update a contact

Updates a contact identified by its id only (its list is derived from the contact). The body is the same flat object as POST /lists/list/{listId}/contacts, with the same key resolution and the same pitfalls: unknown keys create custom variables, null and empty strings are ignored (a field cannot be cleared), sent fields overwrite, absent fields stay untouched. A company row is created if the contact has none and company fields are sent.

No duplicate check is made: changing the email to one already present in the list creates a duplicate. List counters are not updated. The campaigns using the list are resynchronized.

patch/lists/contacts/{contactId}

Request

  • Base URL: https://api.emelia.io
  • URL: https://api.emelia.io/lists/contacts/{contactId}
  • Auth: API key in header Authorization

Path parameters

contactIdstring required

Contact id (leadId).

Request body

ListsContactFields required

Flat contact object: one key per field, scalar values only. Standard keys are listed in the description of POST /lists/list/{listId}/contacts; any other key goes to an existing custom variable of the same name or creates a new one. Numbers and booleans are converted to strings. null and empty strings are ignored. Arrays and objects are rejected.

Example request

{
  "firstName": "John",
  "lastName": "Doe",
  "email": "john.doe@acme.com",
  "companyName": "Acme",
  "icebreaker": "Loved your talk at SaaStock"
}

Response

Contact updated.

successtrue required
leadIdstring required
companyIdstring nullable required

Changes

No recorded changes to this operation across all 1 revision of this API.