For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sessions & rotation

Mobile sessions follow the same model as residential, with one key difference: sesstime can go up to 60 minutes (residential cap = 30). This matches how long a real mobile device typically holds the same carrier-assigned IP.

For the full session model, syntax, and best-practice patterns, see Residential sessions & rotation. The mobile-specific notes are below.

Mobile-specific behavior

60-minute cap

helo_s1a2b3c4d5e-type-mob-region-us-asn-6167-session-job1-sesstime-60

Specifying sesstime > 60 returns 400 + X-Helodata-Error-Code: sesstime-out-of-range.

Higher repinning rate

Mobile devices change cells, lose signal, or switch IPs at the carrier's discretion. Expect the X-Helodata-Session-Repinned: true header more often than on residential — plan for 5–15 % of long sessions to be repinned mid-flight.

Pair sessions with ASN

A session without ASN can drift between carriers if the chosen device drops and a different-carrier device picks up. Always combine session with asn when you need carrier consistency:

helo_s1a2b3c4d5e-type-mob-region-us-asn-6167-session-job1-sesstime-60

Rotation pattern for high-throughput mobile

Mobile pools are smaller; rotating per connection can exhaust a small filtered pool. A workable pattern:

  • Open N sticky sessions, each pinned to one carrier

  • Round-robin requests across them

  • When a session returns more than 3 target errors in a row, mint a new session ID

What sessions do not do (mobile-specific)

  • They don't bypass carrier-side rate limits. Each mobile IP shares the carrier's per-IP quota — sticky sessions concentrate your traffic on one IP, which can trigger the carrier's throttling sooner. Spread across more sessions, not fewer.

Last updated

Was this helpful?