Imports a single contact; if it is an existing contact it updates the contact with just the fields passed in the request with a choice of how to handle the merging of data, otherwise it creates a new contact.
Note: To create a new contact, the request body must contain identifiers.email or identifiers.mobileNumber, even if you use the same identifier in the path. If it does not, the call returns 400 Bad request with the error code contacts:identifierMissing.
Request behaviorThe
identifierspecified in the URL path is used to uniquely identify a contact. This can be a custom identifier or a system contact identifier; contactId, email, or mobileNumber.
Existing contactsWhen we find a contact in the account with the specified identifier, the contact record is updated with any data supplied in the object in the request body.
Deleted contactsWhen we find a contact in the recycled bin with the same identifier that you pass in, we will undelete the contact and update with the passed details.
New contactsIf no contact is found with the provided identifier, the contact is created using the identifiers supplied in the object in the request body. The object must contain either an email address or mobile number in the
identifiersfield.
Specifyingnullfor a field's value clears the fieldOnly pass the fields you require updating for a contact.
We interpret a field passed with a
nullvalue (in other words, an empty field) as an instruction to clear the value for that field.Note: This only works with data fields in this call,not identifiers.
Unauthorized