topic Re: Feedback Regarding API Performance and possible API Caching App in APIs & Integrations

Feedback Regarding API Performance and possible API Caching App

Syncall — Tue, 13 Jan 2026 17:33:33 GMT

Dear HubSpot Community,

I am a networking researcher exploring possibilities to transfer part of my research topics into an actual product as startup. It's mostly about API caching that uses AI to be content-aware enough to prevent staleness. I am posting here because CRMs could be a good target group and I was pointed towards HubSpot and that they have a great Market Place for integrations.

So I was wondering if it makes sense to build a sort of HubSpot "API-Caching" App that (1) just forwards calls to the HubSpot API, (2) returns fast cached versions for repetive calls, and (3) automatically purges the right data from the cache if changes to the data are observed.

This could be an approach to:

reduce HubSpot API latency on cache hits to around 40ms
reduce API call volume to stay below the limits

My question would be, if that would actually provide some value?

The Performance of the HubSpot API is already ok, would an even faster version help?
Do people use the HubSpot API in scenarios where milliseconds matter (e.g., a user-facing frontend) or just async background tasks?
Are API limits an actual issue?

Would love to hear your thoughts!

Re: Feedback Regarding API Performance and possible API Caching App

Victor_Becerra — Wed, 14 Jan 2026 13:18:09 GMT

Hi @Syncall

Thanks for sharing the context — this is an interesting idea, and CRMs are definitely a place where caching can matter depending on the integration pattern.

I’d like to bring a few Community members into the conversation who build integrations at scale and have strong opinions on API performance and rate limits.
@evaldas @RubenBurdin @SteveHTM — hope you’re all having a great week! Have you seen real-world HubSpot integrations where API latency or rate limits become a meaningful constraint (especially in user-facing apps)? And do you think an “API caching proxy” that’s smart about staleness/invalidation would add value, or do most teams already solve this internally with local caching + webhooks?

Would love to hear any perspectives, patterns, or “gotchas” from experience.
Best,
Victor

Re: Feedback Regarding API Performance and possible API Caching App

Syncall — Thu, 15 Jan 2026 10:27:37 GMT

Hey @Victor_Becerra,

thanks for forwarding! These are exactly the questions I am also asking myself.
Best

Re: Feedback Regarding API Performance and possible API Caching App

Victor_Becerra — Thu, 05 Mar 2026 15:46:03 GMT

Hey there @Syncall

Just checking in to see if you managed to find answers to your questions.

In any case, I wanted to share a few Community threads and official resources that could provide helpful insights:

https://community.hubspot.com/t5/APIs-Integrations/Rate-limits-API/m-p/1002704

https://community.hubspot.com/t5/Data-Hub/API-Rate-Limiting-During-Initial-Workflow-Enrollment/m-p/420973

https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines

Hope this helps!

Victor

Re: Feedback Regarding API Performance and possible API Caching App

Syncall — Fri, 06 Mar 2026 13:54:05 GMT

Hey Victor,

thanks for the catch up. I do not have a complete answer but my impression is that the main challenge in CRM systems is the Integration of the APIs and working around rate limits (e.g. with batch requests like as suggested by your linked comment), the actual performance of the API seems to be not that important. So we will focus on other sectors first and come backt to CRMs if it makes sense.
Best

Re: Feedback Regarding API Performance and possible API Caching App

BérangèreL — Tue, 10 Mar 2026 16:51:03 GMT

Hi @Syncall and welcome, we are delighted to have you here! 🧡

To get back to you on this, thanks for your patience, yes, API rate limits are important to keep in mind.

Free/Starter accounts include 250,000 calls per day, Professional offers 625,000, and Enterprise provides up to 1,000,000 daily calls.

Burst limits vary from 100 to 190 requests per 10 seconds per app, so for high-volume integrations, planning for these limits can be helpful.

We encourage caching, as noted in the API guidelines: “If your site or app uses data from HubSpot on each page load, that data should be cached and loaded from that cache instead of being requested from the HubSpot APIs each time.”

Using webhooks is a great option for cache invalidation. The Webhooks API sends real-time notifications whenever CRM data is created, updated, deleted, merged, or associations change, making them a good fit for keeping your cache up to date.

If you’re looking for Community insights on this approach, I'd love to put you in touch with our Top Experts: Hi @Anton, @SteveHTM and @JWingate2 do you have suggestions to share with @Syncall, please?

Thanks so much and have a lovely day!
Bérangère

This post was created with the assistance of AI tools