Mismatching IDs

This page aims to clarify one particular aspect of our API: the names we use to denominate a contact.

We have two types of contacts in our system:

• user contacts - which is our legacy representation of contacts.
• business contact - which the entity any Integrator will receive on their services via webhook.

If you eventually go to our Web UI, and open a contact detail page you might come acros a URL looks like /internal/contacts/f696ec22-cde1-431c-88c8-e013dc9a4cb8. In this URL, the id in the end of that URL points to a user contact. This id will not leave our UI service, therefore won't be sent to your services. We do, however, have another ID, the business contact ID, that's the one that will be sent to your services.

Workaround

We know this is an annoying behaviour caused by our legacy UI service. We are working on this and will eventually unify these two contact types.

As a workaround, in case you want to find a previously-sent contact on your database, consider searching by its email + its business_id.

Note

It is worth mentioning that it only applies to contact. All other ID you will find on the URLs coming from our UI are valid and should match the ones you receive from Data API.