Sticky sessions

✓Residential — supported✓Rotating ISP — supported✓Rotating DC — supported

A session id ties your requests to one exit. Reuse the id, keep the IP.

Soft sticky

curl -x USERNAME:[email protected]:8000 \
  https://api.ipify.org

curl --proxy-header "X-Rayobyte-Session: abc12345" \
  -x us-east.gw.rayobyte.com:8000 https://api.ipify.org

You keep the same exit while it stays healthy. If that device drops off, we give you a replacement and your request succeeds from a different IP.

This is what most people want. Your flow survives a device going offline, at the cost of occasionally moving.

Strict sticky sessions

✓Residential — supported—Rotating ISP — not supported—Rotating DC — not supported

curl -x USERNAME:[email protected]:8000 \
  https://api.ipify.org

Same idea, no substitution. If the exit becomes unavailable the request fails instead of moving.

Use it when a changed IP is worse than a failed request: a checkout, a bank-like flow, anything where the target invalidates the session the moment the address changes. You handle the failure and start the flow again.

Session ids

One to sixteen letters or digits. No hyphens, no underscores, no punctuation. A hyphen starts a new option, and everything after it is read as one.

-session-abc12345        good
-session-worker_7        bad, underscore is not allowed
-session-worker-7        bad, "-7" is parsed as an option

Ids are yours to choose and are scoped to your account. abc12345 from you and abc12345 from another customer are different sessions.

Generate one per concurrent worker. Reusing one id across threads funnels every thread through a single device.

How long they last

Until the default lifetime expires, or until you set one explicitly with -duration-.

Stop sending the id and the session simply stops being used; there is nothing to close.