New required information for the Associations API v3 in developer preview

zwolfson
HubSpot Employee

Edit: March 30, 2020 - This change is now live.

 

What’s happening

When creating, updating or removing associations between CRM objects, you will now need to specify a type of association.  This type will also be returned when requesting associations for an object or a batch of objects.

 

Adding an association to a contact before the change:
PUT/crm/v3/objects/contacts/{contactId}/associations/{associatedObjectType}/{toObjectId}

 

Adding an association to a contact after the change:

PUT/crm/v3/objects/contacts/{contactId}/associations/{associatedObjectType}/{toObjectId}/{associationType}

 

In addition, you can discover what types of associations by using a new endpoint at GET crm/v3/associations/{fromObjectType}/{toObjectType}/types

 

Why is this happening

Associations are an important part of any CRM. For example, being able to accurately reflect how contacts are associated with a company is critical.  Your sales team needs to know if this contact is an advisor to the company or the contractor handling the implementation of your product. Today, the associations API does not support these types of associations, only that the contacts are associated with the company.  Adding this information to the API allows you to build integration that can capture and be aware of this extra context. 

 

When is this happening

This change will take place on Monday March 30th

 

This only affects the API currently in the developer preview program. 

 

If you have any questions, join the conversation here

3 Replies 3
Seth_Israel
Contributor

When this is released can we count on it improving the experience in associating users on Single Page Application Websites and using Segment to integrate HubSpot? We were assured by your team that this release would be a huge help but I shared it with my Engineering team and they called out since we don't use your API that it may not even improve our experience.

Right now no users are automatically associated in chat because we don't use external form tracking nor identify calls with emails, for security purposes. All users must provide email to the automatic question sent to them, or get associated by a representative manually—definitely NOT the ideal experience.

0 Upvotes
zwolfson
HubSpot Employee

Hey @Seth_Israel,

This change does not address the use case you laid out. It seems like there is some confusion as to what releas you are expecting vs what we are putting out.  I'm going to follow up in a direct message to chat about specifics. 

 

This release is about associating CRM objects to each other, not about associating web visits to CRM objects. 

 

Thanks,
Zack

 

Syncari
Participant

What are the valid set of values for fromObjectType & toObjectType?