rate_limited
429 Too Many Requests Too many requests - slow down.
When you get it
Too many requests - slow down. It is always answered with HTTP 429 - one code means one status, so a client may key its handling on either.
Fields it carries
Inside each errors[] entry, beside pointer:
limit- The cap this operation enforces.
window- The rate-limit window the limit applies to.
retryAfter- How long to wait before retrying, in seconds. Mirrors the Retry-After header.
A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.
How to fix it
Slow down. Wait for the Retry-After / RateLimit-Reset the response carries, then retry - do not spin.
Shape
{
"type": "https://api2.host-tracker.com/problems/rate-limited",
"title": "Too many requests - slow down.",
"status": 429,
"code": "rate_limited",
"errors": [
{ "limit": …, "window": …, "retryAfter": … }
]
}