Hi!
I’m writing regarding the “429 Too Many Requests: You have reached your secondly limit.” error that we’re receiving for the public application, which is connected to several HubSpot accounts:
1. Currently, with any of our requests to HubSpot, we receive “429 Too Many Requests: You have reached your secondly limit.” What is the cause of this error for the application?
2. In article, there is information about limits “For OAuth apps, each HubSpot account that installs your app is limited to 110 requests every 10 seconds.” How can we increase this limit for our application?
2.1 Does this limit apply to the entire application in the marketplace or to individual HubSpot accounts using this application? Currently, we are observing errors across all accounts that use this application.
3. Is it possible to reset the request limit to HubSpot at the moment?
Hi!
I’m writing regarding the “429 Too Many Requests: You have reached your secondly limit.” error that we’re receiving for the public application, which is connected to several HubSpot accounts:
1. Currently, with any of our requests to HubSpot, we receive “429 Too Many Requests: You have reached your secondly limit.” What is the cause of this error for the application?
2. In article, there is information about limits “For OAuth apps, each HubSpot account that installs your app is limited to 110 requests every 10 seconds.” How can we increase this limit for our application?
2.1 Does this limit apply to the entire application in the marketplace or to individual HubSpot accounts using this application? Currently, we are observing errors across all accounts that use this application.
3. Is it possible to reset the request limit to HubSpot at the moment?
This error occurs when your application exceeds HubSpot’s API rate limits. For OAuth apps, HubSpot imposes a restriction of 110 requests every 10 seconds per installed account. If your application is trying to send more requests than this limit, you will encounter the 429 error.
This limit applies to each individual HubSpot account using your app, meaning if you have multiple accounts connected to your application, each account is subject to its own limit. This can lead to errors across all accounts if any of them hit their limit. Unfortunately, HubSpot does not offer a way to increase the rate limit for OAuth apps, so the best approach to managing this limitation is to optimize the number of requests your app sends.
You can implement strategies like batch processing to combine multiple requests into one, or use retry logic with exponential backoff to handle situations when the rate limit is reached. Additionally, HubSpot automatically resets the request limit every 10 seconds, so there’s no way to manually reset the limit, but you can adjust your app’s request flow to avoid hitting this limit consistently.
Hi!
What could be the solution when many accounts (more than 30) are using our application and one of them hits the limits?
“This can lead to errors across all accounts if any of them hit their limit.”
This means that all accounts using this application will experience this error.
Reducing the number of requests is impossible as they are already minimal. But due to the number of accounts using one application, the total number of requests is high.
Solution- to create a similar new application and migrate some accounts to it?
Each of your HubSpot API calls to HubSpot relates to only one authenticated portal, so your app should not experience errors in other portals unless your app has difficulty isolating and de-queuing your throttling to each independent portal. Design your throttling code to maximise rate limits per portal, not as a single queue which could suffer head-of-line-blocking.
It is your app’s responsibility to rate-limit the number of API calls per portal to remain within each 3rd-party API rate limit. Respecting rate limits is a key performance metric if you hope to have your app certified by HubSpot one day. If rate limits are a problem, make sure you optimize your calls, for example use batch calls when working with multiple records as suggested by @HMir
At HubDo we implement a per-portal token-bucket throttling mechanism in our public apps. There are many ways to throttle your API requests to respect the rate limit of any 3rd party API. For example: How To Avoid 429 Too Many Requests With NPM Rate Limiting
This error is almost always tied to HubSpot’s per portal OAuth limit: 110 requests per 10 seconds, per connected account (Accounts Dashboard | HubSpot)
The limit isn’t global across all installs of your app, but if your code is funneling requests through a single shared queue, you can get “head-of-line blocking” where one busy portal makes the whole app look throttled
HubSpot doesn’t allow you to “reset” or raise that cap for public apps. The counters automatically refresh every 10 seconds (Accounts Dashboard | HubSpot)
The practical fixes are to implement per-portal throttling, batching endpoints (like the batch Contacts/Companies APIs), and exponential backoff with retries. That way one customer hitting their ceiling doesn’t bring everyone else down.
Splitting into multiple app IDs technically works, but it adds new headaches: managing multiple apps, migrating installs, and keeping scopes aligned. It’s usually better to fix the queuing logic inside the app than to shard installs artificially.
For context, this is exactly the type of problem we designed Stacksync to solve. Instead of building your own token-bucket system and worrying about global outages when one account spikes, Stacksync handles per portal throttling, batching, and retries out of the boox
It basically acts as a buffer so all 30+ accounts can sync safely without hitting HubSpot’s walls. Happy to walk you through a pilot if it’s useful.