Proxy & InfrastructureResidential Proxies
Responses and errors
Understand proxy responses, target status codes, and common proxy failures.
Residential Proxies return the target website response through your HTTP client. There is no WebScrapingAPI JSON envelope for successful proxied requests unless the target site itself returns JSON.
Successful responses
When the proxy request succeeds, your client receives the target response body and status code.
HTTP/1.1 200 OK
content-type: application/json
{
"origin": "203.0.113.10",
"url": "https://httpbin.org/get"
}Error handling
| Status or error | Meaning | Action |
|---|---|---|
407 Proxy Authentication Required | Proxy credentials are missing or invalid. | Check username, password, endpoint host, and port. |
403 Forbidden | Target website or proxy access denied the request. | Check account access, country choice, and target restrictions. |
429 Too Many Requests | Target or upstream rate limits were reached. | Back off, reduce concurrency, or rotate sessions. |
5xx | Temporary target, network, or proxy-side failure. | Retry with exponential backoff and log target URL plus proxy country. |
| Timeout | The target did not respond before your client timeout. | Increase timeout for slow targets or retry with a new session. |
| TLS verification error | Your client rejected the proxied TLS certificate flow. | Follow your HTTP client requirements for proxy TLS verification. |
For troubleshooting, log the target URL, selected country, session identifier, HTTP status, and timing. Do not log proxy passwords.
Treat target status codes separately from proxy connectivity errors. A successful proxy connection can still return a target 404, 403, or 500.