# Hubspot API Ratelimiting

**URL:** <https://community.hubspot.com/t/hubspot-api-ratelimiting/100913>\
**Category:** APIs & Integrations\
**Tags:** oauth\
**Created:** [February 23, 2024, 1:03pm UTC](https://community.hubspot.com/t/hubspot-api-ratelimiting/100913 "2024-02-23T13:03:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SurveySparrow](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@SurveySparrow](https://community.hubspot.com/u/SurveySparrow)\
**Post date:** [February 23, 2024, 1:03pm UTC](https://community.hubspot.com/t/hubspot-api-ratelimiting/100913/1 "2024-02-23T13:03:20Z")

</div>

Hello Community,  
We are having a usecase with hubspot, whenever an action occured in hubspot (for example, contact is created), we have an incoming webhook to our app and then process it to perform some action from our end and we use hubspot api for getting the contact details that is created.  
While we have this action multiple times and the api is hit, we are getting error 429 (Too many requests).  
As noticed in the Hubspot Developer Docs, we found that each HubSpot account using our app is limited to 100 requests every 10 seconds.  
Is there any way to get this resolved or an alternative approach to enable API calls even if the limit is exceeded?

---

<div class="post-metadata">

**Author:** ![dsmarion](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dsmarion/32/7509_2.png) [@dsmarion](https://community.hubspot.com/u/dsmarion)\
**Post date:** [February 23, 2024, 3:20pm UTC](https://community.hubspot.com/t/hubspot-api-ratelimiting/100913/2 "2024-02-23T15:20:09Z")

</div>

Because your app can get hit with an overwhelming number of webhook calls I have heard that most developers do not process them when they get the call. Rather they use some form of queing system where they log the call details and process them afterwards in batches to avoid the issue you have. Maybe someone who has more experience doing this in practice will respond with some suggestions.

---

<div class="post-metadata">

**Author:** ![IgorRubinovich](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/igorrubinovich/32/6240_2.png) [@IgorRubinovich](https://community.hubspot.com/u/IgorRubinovich)\
**Post date:** [May 14, 2024, 3:02pm UTC](https://community.hubspot.com/t/hubspot-api-ratelimiting/100913/3 "2024-05-14T15:02:39Z")

</div>

Hi @SurveySparrow,

please consider [https://www.websemaphore.com](https://www.websemaphore.com) - it was born out of similar requirements and will help you easily scale this type of flow in terms of throughput while staying near-realtime.

Ping me if you’d like to discuss.

Best regards,

Igor

[https://www.linkedin.com/in/igorrubinovich/](https://www.linkedin.com/in/igorrubinovich/)