{"slug":"zyte-api-response-errors","name":"Zyte API: response status and rate limits","category":"diagnostic","provider_slug":"zyte","publisher":"Zyte","publisher_type":"official","website":"https://docs.zyte.com/zyte-api/usage/errors.html","summary":"Separate the API response status from the target website's status and browser-action results.","tools":["python-requests","scrapy"],"capabilities":["error-handling"],"outputs":["Diagnostic guidance"],"connection":"http-api","billing_basis":"Zyte documents rate-limited and unsuccessful API responses as uncharged; a successful API response can still contain a target error.","facts":[{"label":"Two status layers","value":"An API HTTP 200 can carry a target website statusCode of 404.","source_ids":["docs"]},{"label":"Browser actions","value":"An unsuccessful action does not necessarily fail the API request; inspect the actions field.","source_ids":["docs"]},{"label":"Rate limits","value":"API HTTP 429 or 503 can indicate rate limiting. Inspect the response type to determine the limit.","source_ids":["docs"]}],"setup":["Inspect the HTTP response and JSON error type.","Check statusCode and action outcomes before treating returned data as usable."],"limitations":["Successful transport does not establish that the requested extraction meets your requirements."],"sources":[{"id":"docs","label":"Zyte API error handling","url":"https://docs.zyte.com/zyte-api/usage/errors.html","checked_at":"2026-09-27"}],"checked_at":"2026-09-27","review_due":"2026-10-27","evidence":"documented","url":"https://workingproxysites.info/tools/zyte-api-response-errors","provider_url":"https://workingproxysites.info/t/165-zyte-proxies","review_overdue":false}