Guides

Proxies & sessions

Every request leaves Siftzo through a residential proxy. You do not configure proxies yourself; you choose a country, and optionally a session to keep the same IP.

Residential exits

Both tiers, HTTP and browser, send traffic through a residential proxy network. Target sites see an ordinary home-network IP address, never Siftzo's servers. Proxy traffic is included in the credit price; there is no separate bandwidth charge.

Choosing a country

Set country to an ISO 3166-1 alpha-2 code to choose where the request comes from. Sites that show prices, languages or content per region will answer as they would for a visitor from that country.

Request body
{
  "url": "https://example.com/pricing",
  "country": "fr"
}

Without country the exit can be in any country. The code is case-insensitive (DE and de are the same). Siftzo checks the format, but how many IPs are available differs per country, so small countries can see more retries or proxy_unavailable errors.

Sticky sessions

By default every attempt gets a new IP. That is what you want for most scraping, and it lets retries after a block come from a different address.

When you need several requests to come from the same IP, for example to page through results that a site ties to one visitor, pass the same session value on each request:

Request body
{
  "url": "https://example.com/results?page=2",
  "country": "de",
  "session": "crawl_42"
}
  • A session is 1–64 characters of letters, digits and _.
  • Requests with the same session keep the same exit IP for about 10 minutes.
  • Sessions are scoped to your account. Another customer using the same name gets a different IP, and the name you choose is never sent to the proxy provider.
  • Use the same country on every request in a session.
  • Retries inside a request also use the session's IP, so a session that gets blocked stays blocked. Start a new session name to get a new IP.

Sessions control the IP only. Each request still gets a fresh browser profile, so cookies are not carried over between requests. Send the cookies you need in headers.