Today we’re announcing an increase to our API rate limits. These increases apply to accounts with a Professional or Enterprise subscription, the API Limit Increase capacity pack, and also includes changes to the limits for public apps and the CRM Search API.
What’s changing for private apps?
For accounts with a professional subscription the limits are changing:
The daily limit will be increased from 500,000 requests per day to 650,000 requests per day
The burst limit will be increased from 150 requests per 10 seconds to 190 requests per 10 seconds.
For accounts with an enterprise subscription, the new limits will be:
The daily limit will be increased from 500,000 requests per day to 1 million requests per day.
The burst limit will be increased from 150 requests per 10 seconds to 190 requests per 10 seconds.
Additionally, the API Limit Increase capacity pack will add 1 million requests per day to the standard limit, increased from 500,000 requests per day. It will also be possible to purchase the capacity pack twice, allowing for accounts to get an additional 2 million requests above the standard limit. The capacity pack will also increase the burst limit to 250 requests per 10 seconds, up from the previous 200 requests per 10 seconds. The burst limit increase will not stack, so two packs will result in the 250 requests per 10 second limit.
What’s changing for public apps?
For public apps, the burst limit will be increased from 100 requests per 10 seconds to 110 requests per 10 seconds.
What’s changing for the CRM Search API?
The burst limit for the search API will be increased from 4 requests per second to 5 requests per second.
The maximum supported objects per response will be increased from 100 records in the response to 200 records.
These new limits are already in place and active for existing accounts, including the additional limits included with the API add on. These new limits are already reflected in the X-HubSpot-RateLimit-response headers.
Please let us know if you have any questions by replying below.
This announcement highlights significant increases in API rate limits for professional and enterprise accounts, as well as changes to public apps and the CRM Search API. Key updates include higher daily and burst limits for private apps (up to 1M requests daily for enterprise accounts) and the option to expand limits further with capacity packs. As businesses grow, ensuring compatibility with modern frameworks becomes crucial—many are migrating AngularJS to Angular to boost performance and scalability, aligning with such updates. Public apps see a slight burst limit increase, while the CRM Search API benefits from increased burst rates and doubled response object capacity. These changes are already in effect, aiming to support greater flexibility and scalability for API users.
Hi,
Is there a way to increase the limit for our public app? which has the burst limit will be increased from 100 requests per 10 seconds to 110 requests per 10 seconds.
It’s pretty striking to look at this again in 2025.
A lot has shifted: data volumes are only going up, and teams are wiring HubSpot into more operational systems than ever.
The increase HubSpot rolled out back in 2023 felt big at the time, but by 2025 most orgs I work with treat 1M requests/day as table stakes, especially when syncing product usage events, ERP data, or real-time engagement metrics. The extra burst capacity is welcome, but the bigger story now is how to design around limits so you’re not firefighting when usage spikes.
That means batching intelligently, leaning on the expanded CRM Search (200 records per call is a lifesaver), and monitoring headers closely to catch when you’re close to ceilings
For 2025, the real differentiator isn’t just “more requests,” it’s making sure your sync layer handles retries, backoff, and transformations without engineering teams constantly patching pipelines. If your growth plans involve multiple systems feeding HubSpot, it’s worth thinking in terms of resilient two-way sync. That way, HubSpot stays consistent in real time while you scale usage beyond what burst math alone can guarantee