Residential Proxy Guide
Setup, targeting, rotation, and code examples
Overview
IPLoop's residential proxies route your requests through 100M+ real residential IPs across 195+ countries. These are IPs from real devices — not datacenter servers — making them ideal for web scraping, ad verification, and market research.
Proxy Endpoints
| Protocol | Host | Port |
|---|---|---|
| HTTP / HTTPS | proxy.iploop.io | 8880 |
| SOCKS5 | proxy.iploop.io | 1080 |
Authentication Format
customer-{CUSTOMER_ID}-{PARAMETERS}:{API_KEY}
Parameters are optional and chained with dashes:
| Parameter | Example | Description |
|---|---|---|
cc-XX | cc-US | Target country (ISO 3166-1) |
city-NAME | city-miami | Target city |
sesstype-TYPE | sesstype-sticky | Session type: sticky or rotating |
lifetime-MIN | lifetime-30 | Sticky session duration (minutes) |
session-ID | session-abc123 | Custom session identifier |
Session Types
Rotating (Default)
Every request gets a new IP. Best for scraping large volumes of pages.
curl -x proxy.iploop.io:8880 \ -U "customer-YOUR_ID-cc-US:API_KEY" \ https://httpbin.org/ip
Sticky Sessions
Keep the same IP for a set duration. Best for multi-step workflows (login, checkout, etc.).
curl -x proxy.iploop.io:8880 \ -U "customer-YOUR_ID-cc-US-sesstype-sticky-lifetime-30:API_KEY" \ https://httpbin.org/ip
Sticky sessions last up to 30 minutes. If the peer disconnects, you'll get a new IP automatically.
Country Targeting Examples
# United States customer-YOUR_ID-cc-US:API_KEY # Germany customer-YOUR_ID-cc-DE:API_KEY # United Kingdom, London customer-YOUR_ID-cc-GB-city-london:API_KEY # Japan, Tokyo with sticky session customer-YOUR_ID-cc-JP-city-tokyo-sesstype-sticky-lifetime-10:API_KEY
Best Practices
- Use rotating sessions for high-volume scraping
- Use sticky sessions for workflows requiring the same IP
- Always specify a country for better performance
- Monitor your usage on the Analytics page to optimize costs
- Use SOCKS5 for non-HTTP protocols