Update Contact

Tool name: update-contact-values

Updates explicitly listed contact-field values for one contact. It cannot change email or SMS addresses, opt-in state, subscriptions, lists or other channel data. Every custom-field ID and the contact itself must belong to the selected account; global contact fields remain available. Date, time and datetime fields take the forms get-contact answers with -- 16.09.2026, 16.09.2026 14:30, 14:30 -- and ISO 8601 as well, for a caller that computed a date rather than read one. Anything else is refused rather than stored as a date it was not meant to be, and the refusal names the form that works. An empty value clears the field.

Input schema

contactIdinteger, >= 1required

Numeric contact ID returned by search-contacts

fieldsArray of objects, [ 1 .. 50 ] itemsrequired

Contact field updates; fieldId must be a global field key or an account-owned numeric custom-field ID, a date, time or datetime value takes the form get-contact answers with, and referenceId defaults to 0

accountIdnull or integer, >= 1

User ID of the account; omit for the account the access token works in

Default:null

Input example

{
  "contactId": 1,
  "fields": [
    {
      "fieldId": "string",
      "value": "string",
      "referenceId": 0
    }
  ],
  "accountId": null
}

Output schema

updatedFieldIdsArray of stringsrequired

contactobjectrequired

Output example

{
  "updatedFieldIds": [
    "string"
  ],
  "contact": {
    "accountId": 0,
    "contactId": 0,
    "email": "string",
    "subscriptionStatus": "string",
    "referenceId": 0,
    "fields": [
      {
        "fieldId": "string",
        "value": "string",
        "type": "string",
        "referenceId": 0
      }
    ],
    "manualTagIds": [
      0
    ],
    "editUrl": "string"
  }
}