Skip to main content
Sessions control how long you hold the same residential IP.
  • Rotating — every request gets a fresh IP (default)
  • Sticky — the same IP is held for a configurable TTL

Rotating (default)

Without a session modifier, each request pulls a new IP:
Good for: scraping, SERP collection, broad crawls.

Sticky sessions

Append -session-<id> to your username. Same ID = same IP.

Session TTL

Control how long the session holds the same IP with -ttl-<minutes>:
After the TTL expires, the next request with that session ID starts a new session with a fresh IP. Residential uses ttl-<minutes>. Datacenter uses duration-<seconds> — see Datacenter. If the assigned IP drops off the network before TTL expires, a new IP is assigned and the session continues seamlessly.

Combining with targeting

Pins a Westlake Village IP for 15 minutes.

Picking session IDs

Alphanumeric, 6–16 characters. Same ID = same IP. Good: 5s5d4xud, bot-nyc-01, a4f8c2e1, sess-7xk9m2 Avoid:
  • Spaces or special characters ($, @, :, /)
  • Sequential IDs (session-1, session-2) if isolation matters
  • Reusing IDs across unrelated workflows

Code examples

When to use each mode

Use the shortest TTL that covers your workflow. Shorter sessions recycle IPs faster and reduce the chance of a flagged IP affecting many requests.