ETA on engagements in v3 API

SOLVE
alansp
Participant

Can I get an ETA on this? It's killing me that we still can't do decent filtering on engagements via API, and I was shocked to learn that v3 had huge gaps in it.

1 Accepted solution

Accepted Solutions
WendyGoh
Solution
HubSpot Employee

Hey @alansp,

 

The latest update I gathered form our team is that we are still working on this release and  haven't set a release date as of yet.

 

I'd encourage you to subscribe to the developer changelog for a notification once its available: CRM API | Engagements

 

 

View solution in original post

0 Upvotes
5 Replies 5
WendyGoh
Solution
HubSpot Employee

Hey @alansp,

 

The latest update I gathered form our team is that we are still working on this release and  haven't set a release date as of yet.

 

I'd encourage you to subscribe to the developer changelog for a notification once its available: CRM API | Engagements

 

 

View solution in original post

0 Upvotes
alansp
Participant

OK. Disappointing, but I appreciate the update.

0 Upvotes
TanguyM
Member

Still no news ? I'd like a decent filtering of engagements via API to use Alan's words once again...

Tanguy

0 Upvotes
dennisedson
Community Manager

@TanguyM , the engagements api is being pulled out into their own CRM object so it is taking some extra time to ensure that the i's are dotted and t's are crossed.  Thanks for the patience. 

Thanks,

Dennis




Check out our Community Developer Blog
where we feature our Community driven developer podcast and how to content
0 Upvotes
PMac
Participant

@dennisedson, is there a suggested work around for this? We have held off completing HubSpot integration with our systems since v1 was deprecated.  It's really becoming an issue for us. We are now going with v1s implementation (https://legacydocs.hubspot.com/docs/methods/engagements/get_associated_engagements) as at least this will return all the engagements in a single call (or worse case at least paged). Am I correct in thinking the current method is fetch all engagement IDs for a contanct, then a seperate API call per engagement to get the details? Can you tell me when the v1 deprecated version will actually go offline?

0 Upvotes