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.
@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?
@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.
Is there any further progress on the migration of the legacy Engagements API v1 into CRM Engagements v3?
The original query was in July 2020, so it would be useful to get some idea on timeframes and/or whether time needs to be invested in creating integrations to support both v1 and v3 APIs, as we are currently using the API to fetch pipelines and deals from v3 and would like to include engagements too.