Hello Team,
Hubspot Serach API documentation says that The search endpoints are rate limited to five requests per second (Account level). Can you please elloborate on this? What is meant by Account level? Lets say if an account has 10 users and each user makes a serach request at the same time, will it result in error as its 10 serach requests per second. Please provide an example of this for better understanding.
Thanks in advance for your timely respone.
@SBalabhadrapa wrote:
Hello Team,
Hubspot Serach API documentation says that The search endpoints are rate limited to five requests per second (Account level). Can you please elloborate on this? What is meant by Account level? Lets say if an account has 10 users and each user makes a serach request at the same time, will it result in error as its 10 serach requests per second. Please provide an example of this for better understanding.
Thanks in advance for your timely respone.
@louischausse @dennisedson @Mike_Eastwood @HubDoPete @Teun
It means that the limit applies collectively to all users and integrations within a single HubSpot account. This means if an account has multiple users or integrations making search requests simultaneously, the total number of requests cannot exceed five per second. For example, if an account has 10 users and each user makes a search request at the same time, it would result in 10 requests per second. Since this exceeds the limit, some of these requests will fail, likely returning a rate limit error.
Hi @SBalabhadrapa , good question. “Account level” means the 5 requests per second cap is shared by everything under one HubSpot account (one HubID).
If 10 users hit the Search API at the same second, the account is still capped at 5 rps, so some calls will 429. See the CRM Search API guide
(Accounts Dashboard | HubSpot) and the 2024 changelog noting the 5 rps and new 200 record page size (Increasing our API limits).,
Practical advices so you don’t fight the limiter: use the maximum 200 records per page and paginate with after to cut round trips, cache hot queries, and centralize a shared throttle across users and services. On 429, back off and retry rather than parallelizing more
The Search API also caps any single query at 10,000 results, so design your filters accordingly. Docs and community threads cover these limits (Accounts Dashboard | HubSpot)