Proxy
Proxy access
Point your own HTTP client, headless browser or scraping framework at Siftzo's residential network. You keep your code; Siftzo provides the IPs.
Endpoint
Hostproxy.siftzo.comPort8443for an HTTPS proxy (TLS to the proxy, recommended), or8090for a plain HTTP proxy.Username- Your key's public id followed by routing parameters, for example
KEY_ID-pool-residential-country-de. The Proxy page in the dashboard shows the id of each key. Password- Your API key (
sz_live_…). The part after the key id works too.
On port 8090 the API key travels in clear text to the proxy, like with every plain HTTP proxy. Use port 8443 whenever your client supports HTTPS proxies, and use a separate key for the proxy so you can revoke it on its own.
Routing parameters
The username is dash-separated pairs. Values are letters, digits and _.
poolstringrequiredresidential: home-network IPs.countrystring- ISO 3166-1 alpha-2 code of the exit, e.g. de. Without it the exit can be in any country.
sessionstring- 1–64 characters. Connections with the same session keep the same exit IP for about 10 minutes. Sessions are scoped to your organization and never sent to the upstream network.
Examples
curl -x "https://proxy.siftzo.com:8443" \
-U "KEY_ID-pool-residential-country-de:$SIFTZO_API_KEY" \
https://httpbin.org/ipimport os
import requests
proxy = f"https://KEY_ID-pool-residential-country-de:{os.environ['SIFTZO_API_KEY']}@proxy.siftzo.com:8443"
r = requests.get("https://httpbin.org/ip", proxies={"http": proxy, "https": proxy})
print(r.json())import { fetch, ProxyAgent } from "undici";
const dispatcher = new ProxyAgent({
uri: "https://proxy.siftzo.com:8443",
token: "Basic " + btoa("KEY_ID-pool-residential-country-de:" + process.env.SIFTZO_API_KEY),
});
const res = await fetch("https://httpbin.org/ip", { dispatcher });
console.log(await res.json());import { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "https://proxy.siftzo.com:8443",
username: "KEY_ID-pool-residential-country-de-session-checkout_1",
password: process.env.SIFTZO_API_KEY,
},
});Billing
Proxy traffic costs 6 credits per MB (1,000,000 bytes), counting bytes in both directions, from the same monthly credits as the APIs. Traffic is added up over the month and rounded up once, so many small connections do not each round up. Connections that fail before a tunnel opens cost nothing.
Credits are reserved in chunks while data flows. When the month's credits run out, or the key's team reaches its cap, open tunnels are closed and new connections get 402. A team key's traffic counts toward the team's cap like its API requests. Each connection shows up in your request logs with tier proxy.
Limits
- Each open connection takes one of your plan's concurrent request slots, shared with the APIs. See rate limits.
- A tunnel stays open for at most 10 minutes.
- Only ports 80 and 443 can be reached. Private addresses, internal names and blocked domains are refused.
- The proxy forwards traffic as it is. Retries, browser rendering and block detection are what the Scraper API adds on top.
Errors
The proxy answers CONNECT with these statuses before any tunnel is opened:
400- The username has an unknown or malformed parameter, or the request is not CONNECT or an absolute http:// URL.
402- The organization's monthly credits, or the cap of the key's team, are used up. A running tunnel is closed when the next chunk cannot be reserved.
403- The account is suspended, the pool is not available, or the target is blocked or not on port 80 or 443.
407- Missing or wrong credentials, or a revoked key.
429- Too many open connections (your plan's concurrency) or new connections opened too fast.
502, 503, 504- The exit could not reach the target, or no exit was available. Retry, usually with a new session.
The responsible use rules apply to proxy traffic like to every other request. Abuse reported to us is traced to the key that made the connection.