Authentication

There are two ways to prove a request is yours. Pick one per product.

Username and password

The default. Your credentials are in the dashboard under Proxy Access → Proxy Parameters.

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

Targeting options are appended to the password:

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

Your real password still authenticates, because we strip the modifier run before checking it. You never rewrite the username.

IP whitelisting

Register the addresses your traffic comes from and send no credentials at all. Targeting then moves into X-Rayobyte-* headers.

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

Set it up under Proxy Access → IP Authorization. Full detail: IP whitelisting.

Caution

SOCKS5 has no request headers. Under IP authorization over SOCKS5, put your targeting in the password field of the SOCKS5 auth instead. See Protocols.

Which to use

Use IP whitelisting when your traffic leaves from a fixed set of servers. There is nothing to leak into a log or a repository, and it is one less string to rotate.

Use username and password when your egress IP moves: laptops, CI runners, autoscaling workers, anything behind a NAT you do not control.

Keep credentials out of your code

Read them from the environment. A proxy password in a committed file is a password you will be rotating on someone else’s schedule.

export RAYOBYTE_USER=...
export RAYOBYTE_PASS=...
curl -x "$RAYOBYTE_USER:$RAYOBYTE_PASS@us-east.gw.rayobyte.com:8000" https://api.ipify.org