A Residential Proxy API Shortlist Built to Cut Wasted GB

What Does a Residential Proxy API Actually Do?

A residential proxy api is the control layer of a residential proxy service: one endpoint your traffic goes through, plus the rules that decide which country, city or ASN you exit from, how long a single IP is held, and who on your team can spend bandwidth. In most providers those rules live entirely inside the proxy username. A few add a REST API on top for sub-users, traffic caps and usage data.

How These Residential Proxy APIs Differ

Every provider here sells the same raw material: IPs on consumer connections. They differ on four things you touch in code, and a 2026 provider survey found 65.8% of scraping professionals increased proxy usage year over year while 43.1% now run two or three providers in parallel. The comparison is less about a single winner than about knowing which lever each vendor gives you.

• Where targeting lives. Country, city, ZIP, ASN and geohash flags are appended to the username, not sent as a separate call. Your credential string becomes versioned configuration.
• How sessions are held. Rotation can happen per request, per session ID, or be pinned to one node that fails instead of silently moving. That decides whether a multi-step login survives.
• How authentication works. Credentials travel with the request and can change per call. IP allowlisting is simpler but fixes your egress address, so per-request targeting is out.
• How traffic is billed. Per-GB rates, header-inclusive metering, per-IP monthly rates for ISP proxies and unlimited plans all appear below. Read the meter definition before the price.

Prices move with commitment, so treat any figure as a starting point. If cost is your main filter, this residential vs datacenter proxies breakdown sets the baseline, because the two are priced on different units entirely.

Nine Residential Proxy APIs, Ordered by Control

Ordered by how much of rotation, targeting and account management you can drive programmatically. Prices are vendor-reported or third-party reported where marked; re-check the official page before committing volume.

1. Oxylabs — deepest credential-level control

Everything routes through one backconnect node, pr.oxylabs.io:7777, and behaviour changes by editing the username. cc, city, st, postalcode, ASN and geohash set the exit location. sessid holds one IP for 10 minutes by default, sesstime stretches that to as long as 1440 minutes, and sessid_oneip pins a session to one node and returns a 502 if it drops. The Oxylabs residential proxy docs also document OS and ipversion filters.

• Pros: ZIP and geohash targeting, day-long sessions, fail-closed node binding, and a location endpoint at ip.oxylabs.io/location returning IP, ASN, city and timezone.
• Cons: the username is configuration you must log per run, and the 502 path needs explicit retry logic.

How Send.win Helps With Residential Proxy Api

Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.

• Isolated profiles – separate cookies, storage and sessions per profile
• Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
• Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
• Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
• Team sharing – share a signed-in profile with a teammate without sharing the password

Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).

Best for: teams that want targeting and stickiness set entirely from code.

2. Bright Data — biggest advertised pool, commitment pricing

Bright Data advertises 400M+ rotating residential IPs across 195 countries, with country, state, city and ZIP targeting at no extra charge, and requires a KYC step before residential use. Bandwidth is billed as request headers plus request data plus response headers plus response data — the widest meter on this list. SOCKS5 is available through its Proxy Manager.

• Pros: the largest advertised pool and coverage here; ISP proxies billed per IP per month (about $1.30 pay-as-you-go, from about $0.90 committed) suit long authenticated sessions.
• Cons: KYC adds onboarding time; header-inclusive metering burns GB faster than most teams plan; pay-as-you-go runs about $8.40/GB per a March 2026 guide, falling toward $3.00/GB at $500+ a month.

Best for: committed monthly volume with a compliance process that can absorb verification.

3. Apify Proxy — residential exits inside the platform

Apify exposes residential IPs through the same single endpoint as its other groups: groups-RESIDENTIAL in the username, country-XX for country and country-US_XX for US states, with sessions holding one IP for roughly 30 minutes. Billing is traffic-based, and the Apify residential proxy docs list the exact syntax.

• Pros: no second vendor relationship if you already run Actors, simple flags, predictable traffic billing.
• Cons: documented targeting stops at country and US state; the session window is not adjustable in the docs; weakest value as a standalone proxy.

Best for: scraping teams already working inside the Apify platform.

4. Decodo — a real management API, free with the plan

Decodo (formerly Smartproxy) publishes an API that creates, updates and deletes sub-users, sets traffic limits, manages IP whitelisting and tracks usage in real time — free with any residential plan. Reported per-GB pricing runs from $3.50 with no commitment down to $2.25 at 100 GB, and the vendor reports under 0.5s average response time with a 99.92% success rate. A Web Data API for scraping and search launched in October 2026.

• Pros: account lifecycle is genuinely programmatic, the API costs nothing extra, and the price ladder is published rather than quoted.
• Cons: the REST surface covers sub-users, limits and usage — per-request targeting still happens in the proxy username.

Best for: provisioning and capping access for several developers without an extra management layer.

5. NetNut — ISP-sourced IPs for stable sessions

NetNut sources residential IPs from ISP connections rather than peer devices, so it competes on latency and session stability instead of pool size. Reported inventory is around 85M residential and 1M static IPs, with a $99/month minimum commitment.

• Pros: lower latency than peer-sourced networks, sessions that hold through long authenticated flows, static IPs alongside rotating ones.
• Cons: the $99 minimum is steep for small jobs, and there is little room to experiment before you are committed.

Best for: dashboards and account management where stability beats pool size.

6. SOAX — city and ISP targeting for verification work

SOAX offers country, city and ISP targeting with rotating and sticky sessions, positioned around a pool for ad verification and research rather than high-volume crawling.

• Pros: ISP-level targeting is rare and useful when you need one specific network, not just a city.
• Cons: less independent benchmark data published than the largest vendors, so test your own targets before scaling spend.

Best for: seeing what a user in a given city on a given network actually sees.

7. IPRoyal — one account across proxy types

IPRoyal sells residential, mobile, ISP and datacenter proxies under one account with traffic-based pricing, aimed at small teams and individual developers rather than enterprise contracts.

• Pros: one vendor and one bill across proxy types; pricing that scales down as well as up.
• Cons: a broad catalogue means more plan comparison before you buy.

Best for: small teams covering residential plus the occasional datacenter or mobile job.

8. Webshare — cheapest way to test the wiring

Webshare reportedly offers a free plan with 10 residential proxies and paid tiers from about $3.50/month for 1 GB, with SOCKS5 support.

• Pros: the lowest-cost entry here, plus a free tier that proves your integration before you pay.
• Cons: 10 proxies and 1 GB go quickly; not built for sustained volume or deep targeting.

Best for: first integration tests, side projects and low-volume jobs.

9. Rayobyte — throughput over precision

Rayobyte markets residential proxies at about $0.50/GB with unlimited bandwidth for high-volume batch jobs.

• Pros: the lowest headline price here; an unlimited model suits batch runs where GB use is unpredictable.
• Cons: check what “unlimited” covers against your job profile before scaling.

Best for: large batch jobs where throughput beats fine-grained geo targeting.

Rotation Windows: Match Session Length to the Job

Rotation breaks more integrations than any other setting, and the default is usually wrong. Rotating on every request is fine for a read-only, stateless fetch; it destroys anything that carries state, because the login lands on one IP and the next request arrives from another. Rotate at task boundaries, not request boundaries, unless the target is genuinely stateless.

Oxylabs gives you 10 minutes of stickiness by default and sesstime stretches a session to 1440 minutes; sessid_oneip refuses to move nodes and returns a 502 instead, which is easier to handle than a silent change of location. Apify holds one IP for roughly 30 minutes. Both patterns work as long as the retry path is explicit — the residential proxy rotation guide covers retry and backoff in detail.

Here is the minimum viable pattern: build the credential string per task, check the exit with one request, then start real work.

import requests

HOST = "pr.oxylabs.io:7777"
USER, PASSWORD = "USERNAME", "PASSWORD"   # your Oxylabs residential sub-user

def proxy_url(session_id, country="US"):
    # cc = country, sessid = sticky IP, sesstime = hold it 30 minutes
    user = f"{USER}-cc-{country}-sessid-{session_id}-sesstime-30"
    return f"http://{user}:{PASSWORD}@{HOST}"

def exit_info(session_id):
    url = proxy_url(session_id)
    proxies = {"http": url, "https": url}
    r = requests.get("https://ip.oxylabs.io/location", proxies=proxies, timeout=30)
    r.raise_for_status()
    return r.json()   # ip, provider, country, city, zip, asn, organisation, timezone

for task in ["order-1041", "order-1042"]:
    print(exit_info(task))

Bandwidth Math: Where Your GB Actually Go

Third-party 2026 comparisons put residential traffic at roughly $2–6 per GB, against $0.10–$0.50 per IP per month for datacenter proxies. That gap only makes sense if you count what you actually download. A fetch that pulls 2 MB of images, fonts and analytics to extract 80 KB of HTML bills 2 MB, and Bright Data’s meter makes this explicit by counting headers and body in both directions.

Residential requests also add 200–1000ms of latency each, against 5–50ms on datacenter, so heavy asset loading costs you twice: once in GB, once in wall-clock time. The fix is the same in Puppeteer, Playwright or a plain HTTP client — block what you do not parse.

Two more levers. Compress: send Accept-Encoding: gzip, br and parse the compressed body rather than disabling compression in the client. Then cache deliberately — re-fetching the same reference page on every run is a billing decision, not a technical one. When you pick a plan size, this guide to comparing residential proxy prices walks through the commitment-tier traps.

Authentication and Targeting: Credentials, Allowlists and Region

Credential auth wins for anything that runs from more than one place. Your CI runner, your laptop and a container all present the same username and password, and the username can carry per-request targeting. Oxylabs accepts four credential formats — HOST:PORT:USER:PASS, USER:PASS@HOST:PORT, IP:PORT:USER:PASS and USER:PASS:IP:PORT — plus bare IP:PORT for whitelisted access.

Allowlisting is simpler to debug and cannot leak into a request log, but it fixes your egress address: no per-call country switch, and a cloud runner with a rotating outbound IP breaks it silently. The pragmatic split is allowlisting for fixed infrastructure and credentials for everything else.

Region is where careful setups still leak. Targeting a US city through the proxy does nothing if the client reports a Warsaw timezone, a Polish locale or a WebRTC candidate on your local network — the exit IP and the environment around it disagree, and that disagreement is visible to the site. Whatever stack you use, align timezone, locale and geolocation to the exit IP and then verify both, because how sites flag a proxy IP is rarely about the IP alone.

Where a Browser Profile Manager Fits — and Where It Doesn’t

A lot of the work people buy residential proxy APIs for is still manual: an agency opening client dashboards, a seller checking five storefronts, a QA team confirming what a logged-in user sees in another region. That work needs separated logins and a sensible exit location, not a per-request endpoint.

Send.win is not on that list, and not because it competes with those vendors: it is a browser profile manager, not a residential proxy provider. Nothing in it is driven from code — there is no automation interface, no SDK, no headless mode and no Selenium, Puppeteer or Playwright integration on any plan. Sendwin Browser runs isolated browser profiles on your desktop — Windows 10/11, macOS 12+, Linux — where each profile keeps its own cookies, storage, sessions, per-profile fingerprint protection and proxy settings. Pro and Team include metered residential bandwidth (5 GB/month on Pro, 20 GB/month on Team), and any profile can instead point at your own HTTP or SOCKS5 endpoint from the vendors above.

Two details matter if you are arriving from a proxy provider. Timezone, locale, WebRTC and geolocation follow the proxy’s exit IP automatically, so you are not setting them per request in code. And the cloud browser runs profiles on Send.win’s server in Helsinki, so a paid teammate can open the same signed-in session from another machine without a password changing hands. Up to 50 profiles open at once on either plan.

The honest division of labour: if you need thousands of requests, dynamic targeting and per-sub-user budget caps, buy one of the services above and drive it from code. If your bottleneck is people opening the same accounts in the same browser, a profile manager solves a different problem — this browser profile isolation explainer covers how separation works at the storage and fingerprint level.

Frequently Asked Questions

What is a residential proxy API and how does it work?

It is the control layer of a residential proxy service: an endpoint you send requests through, plus the rules that decide which IP you exit from and for how long. In most providers those rules live in the proxy username — country, city, session ID, session length — so no separate HTTP call is needed. A few vendors add a REST API on top for sub-users, traffic caps and usage data.

How do I rotate residential proxy IPs from code?

Change the session identifier in the username, or omit the session flag so each request picks a new IP. Oxylabs rotates per request by default and holds an IP once you add sessid; Apify holds one IP for roughly 30 minutes per session. Rotate at task boundaries rather than per request unless the target is read-only and stateless.

How long can a sticky residential proxy session last?

Oxylabs’ sessid holds an IP for 10 minutes by default, and sesstime extends it to as long as 1440 minutes. Apify’s residential sessions hold one IP for roughly 30 minutes. Longer is not automatically better: the longer you hold an IP, the more of your workflow depends on that single node staying reachable.

Should I use username and password or IP allowlisting?

Credentials travel with the request, so they work from laptops, containers and CI runners, and they let you switch country or session per call. Allowlisting is simpler in code but ties you to fixed egress addresses and cannot switch targeting per request. Many teams allowlist fixed infrastructure and use credentials everywhere else — Oxylabs accepts both on the same account.

How do I target a city, ZIP code or ASN through proxy credentials?

Append the targeting flags to your proxy username. Oxylabs uses cc, city, st, postalcode, ASN and geohash; Apify uses country-XX and country-US_XX for US states; Bright Data offers country, state, city and ZIP targeting at no extra charge. Check the exact separator syntax in each provider’s docs before you ship.

What does residential proxy traffic cost per GB?

Third-party 2026 comparisons put residential traffic at roughly $2–6 per GB, with volume tiers below the pay-as-you-go rate. The largest network sits near $8.40/GB on demand per a March 2026 guide, while smaller providers start around $3.50/GB with no commitment. Treat published rates as a starting point and re-check the vendor page before you budget.

How do I verify which IP and location a session is using?

Send one request through the session to a location endpoint before you use it for real work — Oxylabs’ ip.oxylabs.io/location returns IP, provider, country, city, ZIP, ASN, organisation and timezone. Confirm the city and timezone match what your client or browser reports, because a mismatch is what gets noticed. Re-check after any session timeout, since a new exit node means a new location.

Related Products & Resources

• Download
• Demo Browser
• Pricing
• Fingerprint Checker
• Canvas Fingerprint Test