rate_limited

HTTP status 429 · code: rate_limited

The key made more than 60 calls in a minute, or the organisation more than 180 in a minute over all its keys, or repeated failed authentications were throttled. A scan run through POST /v1/domains/{domain_uuid}/scans/{scan_type} answers it too when that domain’s scan of that type was started less than 10 minutes ago.

What the answer carries

Every problem document carries type, title, status, code, detail and request_id. In addition: limit: the limit that was exceeded. Header Retry-After: the seconds to wait.

What to do

Wait for Retry-After seconds, then retry, and slow the job down. For a scan, Retry-After is the seconds left of its 10-minute cooldown, per domain and scan type: back off for that long rather than retrying at once. See rate limits and acting on incidents and scans.