/diagnostic/ — Zyte API: response status and rate limits
Separate the API response status from the target website's status and browser-action results.
Troubleshooting. Official documentation · Checked · Review due .
documented capabilities
HTTP API- Two status layers
- An API HTTP 200 can carry a target website statusCode of 404.[1]
- Browser actions
- An unsuccessful action does not necessarily fail the API request; inspect the actions field.[1]
- Rate limits
- API HTTP 429 or 503 can indicate rate limiting. Inspect the response type to determine the limit.[1]
Billing: Zyte documents rate-limited and unsuccessful API responses as uncharged; a successful API response can still contain a target error.
Outputs: Diagnostic guidance
Documented for: Python Requests, Scrapy
[ official reference ][ provider discussion ][ JSON record ]
checks to make
documentation reviewed- Inspect the HTTP response and JSON error type.
- Check statusCode and action outcomes before treating returned data as usable.
Requirements & limitations
- Successful transport does not establish that the requested extraction meets your requirements.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
1 references- Zyte API error handlingChecked 2026-09-27