We’re using the POST /contacts/v1/contact/batch/ endpoint for thousands of contacts to sync our customers database with Hubspot. The association between our database and Hubspot is based on the email (as the documentation states: “Each set of property data must include either an email address or a vid”)
However, in case of merged contacts in Hubspot, we have some conflicts.
We push a value for a custom field to email@example.com -> it updates the contact with the following id: 961965
We push a different value for the same field to firstname.lastname@example.org -> this is the associated contact: 961963 -> but because the contact is merged, it updates the same contact: 961965
So depending on which updates is made first, we could have at the end a wrong value for our contact email@example.com.
Is there a way (parameter) so that the batch create or update API endpoint does not update merged contacts? (In our example, it does not follow the link 961963 -> 961965.)
Our portal id: 2123903