Device OS targeting

Residential exits are real devices, so each one runs a real operating system. -os- selects on it.

Usage

curl -x USERNAME:[email protected]:8000 \
  https://checkip.amazonaws.com

curl --proxy-header "X-Rayobyte-Os: android" \
  -x us-east.gw.rayobyte.com:8000 https://checkip.amazonaws.com

What our network runs

Primarily Windows and Android today. macOS and Linux coverage is growing, but it is thin. Plan for it to be unavailable in any given country right now rather than assuming a retry will find one.

Value	Availability
`windows`	Broad
`android`	Broad
`linux`	Limited and growing
`macos`	Limited and growing

Aliases

Common spellings are normalized, so you do not have to guess ours.

You send	We match
`win`, `win32`, `win64`	`windows`
`mac`, `osx`, `macosx`, `darwin`	`macos`
`droid`	`android`
`gnulinux`	`linux`

There is no fallback

-os- has no relaxation step. If nothing in the pool matches, the request fails rather than returning a device on a different OS.

That is deliberate. Quietly serving Windows to someone who asked for macOS would be worse than a clear failure. But it does mean a typo fails hard: -os-widows matches nothing and always will.

Pair it carefully

OS combined with a city or a ZIP describes a very small set. If you need OS targeting at volume, keep the geography at country level.

Was this page helpful?