Residential Proxies

Residential proxies route requests through residential IP addresses. Use them when your application needs residential exits and the ability to change the exit IP or retain it for a configured session.

Scrapeless documents HTTP, HTTPS, and SOCKS5 support, geographic targeting, and rotating residential IPs. Your application sends requests through the proxy and receives the target site’s response.

When to use residential proxies

Consider residential proxies for collecting region-specific website content, comparing search or product pages across locations, and distributing independent requests across residential exits.

Choose rotating behavior for independent requests. Choose a sticky session when several requests need to share an exit IP for a limited period. For a dedicated static address, review Static ISP Proxies.

Create a residential channel

1. Sign in to the Scrapeless dashboard and complete any required account verification.
2. Ensure your wallet has sufficient balance.
3. Open Proxy Solutions → Residential Proxy and select Create Channel.
4. Set the channel password and traffic limit, then select Save.
5. Select Start for the channel, configure the available options, and select Generate to obtain the connection details or request example.

See Getting Started for the shared setup walkthrough.

Test the connection

Copy the generated host, port, username, and password into this cURL request:

curl --proxy 'http://YOUR_PROXY_HOST:YOUR_PROXY_PORT' \
  --proxy-user 'YOUR_PROXY_USERNAME:YOUR_PROXY_PASSWORD' \
  'https://api.ipapi.is/'

Replace the four placeholders with the connection details for this proxy type. YOUR_PROXY_USERNAME means the complete generated username, including any options already present. Use the proxy password from that channel.

This example makes an HTTPS request through an HTTP proxy. The response comes from the IP-check service and describes the exit connection it observed. Inspect your actual response; the exit address is not a fixed example value.

Choose a location

Use the location selector to choose a country and, where available, a state or city. The documented username options are country_, state_, and city_.

For example, the official selector maps Australia → New South Wales → Sydney to:

country_AU-state_NSW-city_sydney

Use the selector’s exact codes instead of entering display names. See Geo-targeting for the complete configuration.

The gateway location and exit location are separate choices. Select a nearby gateway for the connection from your application; use the location options to choose the exit. The available regional gateways are listed in Authentication and Endpoints.

Configure rotation or a sticky session

The shared session configuration uses two username options:

The current session guide uses r_0m for rotating requests. For a sticky session, keep the same session ID and use a non-zero duration. Its example, -r_5m-s_test-session-123, requests the same IP for up to five minutes for that session.

A sticky session is time-limited. When the IP expires, a new IP is assigned. See Rotation and Sticky Sessions before designing a workflow that depends on IP continuity.

Keep the generated channel ID and proxy-type identifier unchanged when editing supported options.

Monitor traffic and failures

The official residential billing guide counts both upload and download traffic:

Total data consumption = upload data + download data

Check both the account balance and channel traffic limit if requests stop working. HTTP 407 can indicate invalid proxy credentials or exhausted channel resources. If the proxy reports 525 (no exit found), review the location filters and try a broader selection.

Related configuration

• Authentication and Endpoints: credentials, connection-string fields, and gateways.
• Integrations: connect your application or proxy client.
• Troubleshooting: diagnose authentication, connection, and upstream errors.