Getting started
Learn what residential proxies are, when to use them, and how to send your first proxied request.
Residential Proxies route your requests through real residential IP addresses instead of datacenter IPs. Your scraper still sends a normal HTTP request to the target website, but the outbound connection comes from the residential proxy network.
Use Residential Proxies when your workflow already works with proxy-aware tools and you want more control over the HTTP client, browser, crawler, or automation stack. They are useful for:
- collecting public pages from websites that block datacenter traffic
- testing pages from a specific country or market
- running crawlers that need automatic IP rotation
- keeping the same IP for a short multi-step flow, such as pagination, checkout checks, or session-aware pages
- integrating with tools that accept a proxy URL, such as Playwright, Puppeteer, Scrapy, requests, cURL, browsers, and third-party crawlers
Residential Proxies are different from WebScrapingAPI and Browser API. Those products expose API endpoints that fetch the page for you. Residential Proxies expose proxy endpoints that your own HTTP client uses as its outbound proxy.
Keep credentials server-side
Do not expose proxy usernames, passwords, or generated endpoints in browser code, mobile apps, public repositories, logs, screenshots, or shared notebooks.