Skip to content
Start free

Residential Proxies

Residential Proxies for Web Data Access

Access public pages through residential IPs with country selection, rotating requests and sticky sessions. Keep using your existing HTTP client or crawler.

  • Rotating by default
  • Sticky up to 10 min
  • 4 formats Host:port, HTTP, HTTPS, SOCKS5
  • 2 auth paths Credentials or whitelisted IP
  1. Your clientrequest
  2. WSA endpoint:7777
  3. Residential IPcountry=random
  4. Public webtarget

Buyer fit

Use residential IPs with your existing collector

01

Choose Residential Proxies

You already operate the collection stack.

Keep control of the HTTP client, browser, or crawler while WSA applies the documented residential route and session behavior.

  • Your client accepts an HTTP, HTTPS, or SOCKS5 proxy.

  • You want rotating residential IPs or short sticky sessions.

  • You need documented country selection at the proxy endpoint.

02

Confirm during evaluation

The source, purpose, and request policy still matter.

Confirm that each source and intended use is eligible, then define conservative request, retry, retention, and access rules for your workflow.

  • Review current country and account availability.

  • Test representative targets and response handling.

  • Read the Service Agreement.

03

Consider another path

You want WSA to fetch the page for you.

A request/response API is the clearer fit when your team does not want to own the outbound HTTP client or browser connection.

Connection controls

Connection and location options

Start with one backconnect host, then select authentication, country, session behavior, and an output format accepted by your client.

01

Country

Use country=random for any available documented country, or select one of US, GB, DE, FR, CA, AU, and NL.

02

Authentication

Connect with username and password credentials, or use a whitelisted IP and its documented country host.

03

Output

Generate Host:port, HTTP, HTTPS, or SOCKS5 output according to what your HTTP client, browser, or crawler accepts.

04

Credential handling

Keep credentials server-side. Do not place proxy usernames, passwords, or generated endpoints in browser code, public repositories, logs, or screenshots.

Rotation and continuity

Plan sessions and capacity

Residential access is rotating by default. Omit the session and rotation options when requests do not need to keep the same residential IP.

Default route

Rotate per request

For independent requests, omit session controls and let the endpoint select another residential IP.

  1. rotation=1803 min

    Short handoffs and compact multi-step flows.

  2. rotation=3005 min

    A balanced window for a reused session ID.

  3. rotation=60010 min

    The maximum documented sticky window is 10 minutes.

Developer integration

Connect from your server

Generate one proxy endpoint, store it as a server-side secret, and use it in a proxy-aware HTTP client, browser, or crawler. Your application keeps control of requests, retries, parsing, and storage.

01 Build the endpoint first

One endpoint. Any stack.

Select the account-specific options your client needs, then copy the generated endpoint into a protected environment variable.

Read Residential Proxies docs

Authentication
Credentials or whitelisted IP
Country and session
Set them in the generator
Timeouts and retries
Remain in your application
Credential safety
Keep credentials server-side
import os import requests proxy_url = os.environ["WSA_RESIDENTIAL_PROXY_URL"] response = requests.get( "https://example.com/public-page", proxies={"http": proxy_url, "https": proxy_url}, timeout=30, ) response.raise_for_status() print(response.text)

Set WSA_RESIDENTIAL_PROXY_URL to the generator output. Clients with separate proxy fields use the generated host, port, username, and password.

02

Bring the proxy-aware tools already in your workflow.

Use the generated endpoint wherever your server-side client accepts a proxy configuration.

HTTP clients
cURLrequestsundiciHttpClient
Browser automation
PlaywrightPuppeteerSelenium
Crawlers
ScrapyProxy-aware clients

Operating ownership

One network boundary. Clear responsibilities on both sides.

The proxy endpoint changes the outbound route; it does not take over collection logic or downstream data quality.

WebScrapingAPI

Residential route

WebScrapingAPI operates the residential proxy endpoint, network selection, and the configured rotation or session behavior.

Your team

Collection workflow

Your team operates the HTTP client, browser, crawler, request policy, retries, parsing, storage, and downstream quality rules.

  1. 01

    Choose

    Select an eligible public target and define your request policy.

  2. 02

    Configure

    Generate the endpoint with authentication, country, and session behavior.

  3. 03

    Request

    Your client sends the request through the residential proxy endpoint.

  4. 04

    Operate

    Your team handles the target response, retries, parsing, storage, and quality checks.

Use the service only for eligible public webpages and review source terms, applicable requirements, and the Service Agreement before production use.

Proxy choice

Compare your options

Buyer-fit comparison for residential, datacenter, and ISP proxy routes

Decision

Residential

Datacenter

ISP

Network identity

Real residential IPs

Datacenter-origin IPs

ISP-associated IPs

Documented here

Country choice, authentication, output, rotation, and sticky windows

Confirm the available controls

Confirm the available controls

Continuity

Rotating by default; sticky for 3, 5, or 10 minutes

Confirm for the selected offer

Confirm for the selected offer

Buyer fit

Your team owns the collector and needs residential routing controls

Evaluate when the target accepts datacenter-origin traffic

Evaluate when a workflow needs an ISP-associated route

Swipe horizontally to compare all three proxy types.

Choose Residential Proxies when

your proxy-aware client is already working, your team wants to own request behavior, and a real residential IP route with documented rotation or short continuity matches the workload.

Pricing orientation

Choose a plan for your workload

Self-serve path

Start with a representative request set.

Create an account, generate the endpoint, and test the actual targets, countries, session behavior, response handling, and traffic profile you expect in production.

Evaluation checklist

Confirm the complete operating cost.

  • Expected traffic volume and current plan allowance
  • Country mix and rotating versus sticky requests
  • Client timeouts, retry limits, and failed-response handling
  • Support, account, and contract requirements
Talk to a data expert
What are Residential Proxies?

Residential Proxies route requests from your proxy-aware HTTP client, browser, or crawler through real residential IPs. Your application still chooses the eligible public webpage and processes the response.

What endpoint do I connect to?

For username and password authentication, connect through pr.webscrapingapi.com:7777. The generated proxy URL combines that host with your credentials and selected options.

What happens if I do not set a session?

Rotation is the default. When session and rotation are omitted, each request can receive a different residential IP from the selected country or from country=random.

Which sticky session windows are available?

Sticky sessions use a stable session ID with a rotation value of 180, 300, or 600 seconds, corresponding to 3, 5, or 10 minutes. The maximum documented sticky window is 10 minutes.

Which country values are documented?

Use country=random for any available documented location. The explicitly documented country codes are US, GB, DE, FR, CA, AU, and NL.

How can my client authenticate?

You can authenticate with a username and password in the generated endpoint or use a whitelisted IP with its documented country host and port. Keep credentials and generated endpoints server-side.

Which proxy output formats can I use?

The endpoint generator provides Host:port, HTTP, HTTPS, and SOCKS5 output. Choose the format accepted by your HTTP client, browser, or crawler.

Bring your collector

Find the right proxy for your target sites

Share your target sites, countries, traffic and session needs. We will help match the proxy type and capacity to your collector.