- Rotating — every request gets a fresh IP (default)
- Sticky — the same IP is held for a configurable TTL via a session token
Rotating (default)
Without a session modifier, each request pulls a new IP:Sticky sessions
Append-session-<id> to your username. The <id> is any string you choose — same ID, same IP:
Session TTL
Control how long the session holds the same IP with-ttl-<minutes>:
ttl-<minutes>. Datacenter uses duration-<seconds> — see Datacenter.
If the assigned IP drops off the network before the TTL expires, a new IP is assigned and the session continues seamlessly — no retry needed from your end.
Combining with targeting
Session and TTL stack after country / state / city:Picking session IDs
Use alphanumeric strings, 6–16 characters. Same ID = same IP. Good examples:5s5d4xud, bot-nyc-01, a4f8c2e1, sess-7xk9m2
Avoid:
- Spaces or special characters (
$,@,:,/) — these break URL parsing - Sequential IDs (
session-1,session-2) if you want session isolation - Reusing IDs across unrelated workflows
Code examples
When to use each mode
| Scenario | Mode |
|---|---|
| Scraping many pages across many sites | Rotating |
| Logging into an account and navigating | Sticky |
| Adding items to a cart and checking out | Sticky |
| Querying an API that rate-limits per IP | Rotating |
| Anything that checks session cookies against IP | Sticky |
