We’re trying to create an Tableau analytics dashboard for our business stakeholders where they want to track all the engagements done by our customer advisors. For this we’re using the ‘get recent engagements’ API and we’re successfully able to source the recently updated engagements data.
We’re now working towards ensuring the data stability for the fetched through the Engagement API Calls made via python scripting.
For data verification, we’re comparing the data fetched from the Engagement API with the views present in the Hubspot frontend. Our major focus is on tracking the ‘CALLS’ number here. During this step we came to know that there is a delta when we compare the numbers fetched from the Engagement API (into our snowflake DB tables) with the numbers in the views present in the Hubspot frontend.
Our issue here is that we’re missing out on the records on a daily basis as we’re using the API which as mentioned in the API link max out at 10k records. This data is crucial for our analytics team as it tracks the crucial metrics for our reporting needs. Request the team to please assist us here.
Engagement API Link : Accounts Dashboard | HubSpot
Hi @SimpliZee,
Thank you for getting in touch with the Community!
I understand that when you get the engagements (i.e.: notes, emails, tasks, meetings and calls) via API and you compare with the HubSpot interface there are some records missing on the API results, right?
Regarding sharing data about engagements, are you already using the “Snowflake” integration?
I can see on the documentation that you shared that “the number of items to include in the response. Defaults to 20, has a maximum value of 100”.
I found for you these 2 similar threads that can be of interest to you:
- The solution from @IsaacTakushi on this post “Overwrite the 10k limitation on “get recent engaments” endpoint”
- The solution from @cbarley on this post “Get Recent Engagements API Endpoint”
I also hope to have a couple of subject matter authorities join this discussion @Teun, @ChrisoKlepke and @DanielJeal do you have suggestions to help @SimpliZee, please?
If anybody else has anything to add and/or share, please feel free to join in the conversation 
Thanks and have a fantastic day!
Best,
Bérangère
Hello Berangerel,
Thanks for taking the time out and looping in the subject matter authorities here for the ticket.
While I await for their understandings and solutions, I tried the solution given by @IsaacTakushi on this post “Overwrite the 10k limitation on “get recent engaments” endpoint”. The issue here would be that it’s dependent on the fetching the contacts first. We already are sourcing contacts table at our end and I checked the columns present for engagement related metrics/columns.
Going through the list of engagements columns, I believe that the contacts table will store either the first or the latest engagement Ids and not the engagements in between which we might lead to data leakage for our reporting.
Do let us know if that’s the case or we are looking at it from an incorrect perspective while we await for the subject matter experts opinion on this issue.