GoHighLevel enforces 100 req / 10s and 200,000 req / day per location on API v2. Bulk workflow triggers frequently trip the burst limit.
GoHighLevel enforces 100 req / 10s and 200,000 req / day per location on API v2. Bulk workflow triggers frequently trip the burst limit.
Add exponential backoff (respect `Retry-After`), batch contact updates, or move heavy jobs to workflow queues instead of the API.
GoHighLevel's Funnels & Websites builder, workflow webhooks, or the API v2 responses.
GoHighLevel (HighLevel) — all-in-one agency CRM & funnels platform.
The client has sent too many requests in a given time window — the canonical rate-limiting and abuse-protection status code.
HTTP 429 Too Many Requests is what servers send when a client exceeds a rate limit. It's the polite way of saying "slow down" — and unlike 503 (which says "we're overloaded"), 429 specifically signals that this client has been quota'd, not that the server is in trouble. Well-behaved 429 responses include a Retry-After header telling the client exactly when to retry, plus optional rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) that let clients self-pace before they hit the limit. APIs use 429 heavily; user-facing websites use it during attacks, brute-force login attempts, or scraper abuse.
If Googlebot receives 429, it interprets it as "back off and crawl less" — and it does, sometimes for weeks. A pattern of 429s in Search Console's crawl-stats report can reduce crawl rate sitewide, which slows indexing of new and updated pages. Use 503 with Retry-After for genuine overload (Google handles this gracefully); reserve 429 for actual abuse from specific clients. Whitelisting Googlebot, Bingbot, and other major crawlers in your rate-limit rules is best practice.
LemWatch respects rate limits when monitoring your sites — we use a low default check frequency and back off on 429. If you're seeing 429s in our logs, it usually means another monitoring tool (or a scraper) is hitting the same IP we are.