Raw mode
GET /v1/raw returns the target's body and status exactly as they are. Our figures travel in response headers. Use it when you want to pipe a page or a file straight into another tool.
curl -i "https://api.virginproxy.com/v1/raw?url=https%3A%2F%2Fhttpbin.org%2Fip" \
-H "Authorization: Bearer $VP_KEY"HTTP/2 200
content-type: application/json
x-vp-request-id: req_4tyqEH939pSTwPEWg0ZH
x-vp-exit-ip: 109.41.243.222
x-vp-carrier: Vodafone
x-vp-bytes-down: 4212
x-vp-bytes-up: 1984
x-vp-duration-ms: 524
x-vp-credits: 1
{
"origin": "109.41.243.222"
}Query parameters
| Parameter | Meaning |
|---|---|
url | The target URL, URL-encoded. Required. |
session | Session name, as in POST /v1/requests. |
fresh_ip | true or 1 for a new IP first. |
ip_version | 4, 6 or auto. |
timeout_ms | Timeout in milliseconds. |
Raw mode always sends a GET without custom headers. For other methods, headers or a body use POST /v1/requests.
Status codes
The HTTP status of the reply is the target's status, so a 404 from the target arrives as 404. To tell the target's errors from ours, look for the X-VP-Request-Id header: it is present only when the target answered. Our own errors are JSON with an error object, as described in Errors.
Only the target's Content-Type is passed on. If you need its other headers, use POST /v1/requests.