Gateway & authentication

Every Residential Proxies request goes through one endpoint. You authenticate on each request with your username and password.

Endpoint

Field	Value
Host	p.shifter.io
Port	443
Protocols	HTTP(S), SOCKS5

Use the same host and port regardless of location, protocol, or session mode. Targeting and session options are encoded in the username, not in a different endpoint.

Authentication

Your username and password are shown in the panel under Residential Proxies.

curl -x customer-USERNAME-sid-9f3a2b7c-ttl-600:PASSWORD@p.shifter.io:443 \
  https://ipinfo.io/json

Extend the username with flags to express targeting and session intent:

customer-USERNAME-country-us-city-new_york-sid-9f3a2b7c              # default 120s sticky
customer-USERNAME-country-us-city-new_york-sid-9f3a2b7c-ttl-600      # custom 600s sticky

Flag order does not matter. ttl is optional and only valid alongside sid. The password stays the same regardless of flags.

Common errors

Response	Likely cause
407 Proxy Authentication Required	Username or password wrong, or an unknown flag (e.g. bad country code).
502 Bad Gateway	No IPs match your filter at this moment. Broaden the filter, retry, or remove strict-true to allow a broader fallback.
509 Bandwidth Limit Exceeded	Plan bandwidth exhausted with Extra Traffic disabled.
Connection refused	You are pointing at the legacy port-based host. Switch to p.shifter.io:443.

Next

• Geo-targeting, country, city, ASN syntax.
• Sessions, sticky vs rotating.