While working on developing my public app, I started getting 429 error responses from the API requests. Even though I only sent like less than 10 requests in the last hour.
Is this an issue from HubSpot’s side? Is anyone else facing a similar issue? Or is it only for me? And if so, would you have any idea why?
As of now, this is happening on two different apps I have installed, and on a different app a colleague has installed (from his own developer account). If anyone can provide a sanity check that this is a critical HubSpot issue, I’d appreciate it :')
@BérangèreL would appreciate your guidance on this 
Hi @Sadat and all,
Thank you for your feedback and for the tag - we are experiencing some issues with the CRM Search API.
Our teams have been made aware of this and resolving the issue is currently our top priority.
We’re sorry for the inconvenience and I’ll keep you posted as soon as possible!
Thank you for your patience!
Best,
Bérangère
Seems to be happening for search APIs, but not other APIs.
I checked the Search API rate limit, and I’m still no where near it.
Same problem. Sorry to hear you have this issue but happy to hear this is not just us. Seems there is an issue at the moment.
We’ve hit the same problem, multiple people are affected.
It all started 28 Jan 02:00 UTC for all of them.
I’m also seeing this issue currently for our application and nothing has changed on our end. This seems to be occurring since sometime last evening.
We noticed that if we do a wildcard search, for example, *string*, it throws the 429 error.
We had to change our code to only do a * at the end “string*****” query, which resolved our 429 errors.
But the *string* it did work up until yesterday when something broke.
Hi @Sadat, @PieterVHeerden, @JSweeney8, @SM936, @MouseMedia, @rvarnfors and all,
Thank you for your patience!
Great news, this is now solved and you should no longer see this error on the API search!
Here is the updated Status page about it: “Public API search was unavailable for some users”.
Thank you and have a wonderful day!
Best,
Bérangère
Hi @Sadat
good question here. A 429 from HubSpot normally just means you’ve hit the documented limits on the API (for example the CRM Search API has both a per-second and per-day quota: API usage guidelines and limits - HubSpot docs
In this case though, you and several others were seeing 429s even when under those limits so this was indeed a HubSpot side issue, and it’s now been resolved (confirmed on their status page).
For future builds it’s worth planning for this kind of hiccup. Even when you’re inside the quota, APIs can throttle or misbehave for short periods.
Best practice is to add exponential backoff and queuing so that transient 429s don’t break your app. HubSpot’s own docs on retry logic are here: API usage guidelines and limits - HubSpot docs
That’s actually one of the reasons we built Stacksync. It acts as a managed sync layer that automatically handles retries, backoff, and resiliency for HubSpot integrations. So if HubSpot throws unexpected 429s, the sync just pauses and resumes safely instead of stalling your systems.
Teams using it avoid having to code and maintain all that middleware themselves.
Hope that clarifies why you saw the errors and how to make your integrations a bit more resilient going forward.