Proxies

PagePry can route your scrape requests through proxy networks to bypass geo-restrictions and bot detection.

Proxy types

`none` (default)

Requests are made directly from PagePry's infrastructure. Best for sites with no bot detection or access restrictions.

Credit cost: +0 credits

`datacenter`

Requests are routed through datacenter proxy IPs. Good for:

Bypassing basic IP-based rate limiting
Accessing geo-restricted content
General-purpose scraping at moderate cost

Credit cost: +5 credits per request

`residential`

Requests are routed through residential IP addresses. These appear as real consumer connections and have the highest success rate against bot detection. Best for:

Sites with aggressive bot detection (Cloudflare, PerimeterX, DataDome)
E-commerce sites that block datacenter IPs
Search engines and social media platforms

Credit cost: +25 credits per request

Usage

Set the proxy parameter in your request:

curl -X POST https://api.pagepry.com/v1/scrape \
  -H "x-api-key: pp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com",
    "proxy": "residential"
  }'

Choosing a proxy

Scenario	Recommended proxy
No bot detection	`none`
Basic rate limiting	`datacenter`
Geo-restricted content	`datacenter`
Cloudflare / bot protection	`residential`
E-commerce product pages	`residential`
Search engine results	`residential`

Plan availability

Plan	Proxy access
Starter	Datacenter
Growth	Datacenter + Residential
Business	All
Enterprise	Dedicated pools

Proxy errors

If a proxy connection fails, you'll receive a 502 PROXY_ERROR. These are usually transient — retry the request. If errors persist, try switching proxy types or contact support.

On this page