Developer docs.
Rift exposes standard SOCKS5 and HTTP/HTTPS CONNECT endpoints with user:pass auth — no SDK, no custom client. Drop the proxy URL into any HTTP client, browser or bot and you're live.
Quickstart
Create a credential in the console → Credentials, then route a request. Replace USER / PASS with your generated values.
curl --socks5-hostname USER:[email protected]:1080 https://api.ipify.orgEach request rotates to a fresh exit IP from your pool. That's it — you're routing through Rift.
Authentication
The gateway authenticates with HTTP Basic / SOCKS5 username-password (RFC 1929). Generate per-app credentials in the console — each is independently revocable, and you can hold up to five active at once.
- Username — issued per credential (e.g.
rift_ab2c4d). - Password — shown once at creation; store it in a secret manager.
- Credentials are tied to a pool tier (Budget or Premium) at creation.
Endpoints
One host, two protocols. Both carry the same pools and session semantics.
Host: gateway.riftproxy.com · SOCKS port 1080 · HTTP port 8080. Idle connections are held for 10 minutes.
Pools & tiers
Two datacenter pools, selected when you create a credential. Both speak SOCKS5 + HTTP/HTTPS CONNECT.
Aggregated multi-source pool. Lowest cost — ideal for testing and high-volume bulk work on low/mid-defence targets.
Curated, authenticated datacenter pool. Cleaner IPs, higher uptime, 5-minute dead-IP cooldown.
Datacenter pools suit catalogs, public APIs, price feeds and cart races — not sites running aggressive bot management (Cloudflare, DataDome), which need residential. New accounts get 1 GB free on Budget.
Sticky sessions
By default every request rotates. To hold one exit IP, append -session-<token> to your username. The same token always maps to the same upstream IP; a different token gives a different IP. Tokens are arbitrary (alphanumeric, dash, underscore — up to 64 chars).
curl --socks5-hostname USER-session-checkout1:[email protected]:1080 https://api.ipify.orgThe exit holds for the session as long as the upstream pool is unchanged (refreshed hourly).
IP whitelisting
Optionally restrict which source IPs may use your credentials. Add entries in the console → Whitelist. With zero entries, all source IPs are allowed; once you add one, only listed IPs (or CIDR ranges) can authenticate.
- IPv4 and IPv4 CIDR (e.g.
203.0.113.0/24) supported. - Applies on top of user:pass — both must pass.
Code examples
import requests
proxies = {
"http": "socks5h://USER:[email protected]:1080",
"https": "socks5h://USER:[email protected]:1080",
}
r = requests.get("https://api.ipify.org", proxies=proxies, timeout=30)
print(r.text)import { ProxyAgent, request } from "undici";
const agent = new ProxyAgent("http://USER:[email protected]:8080");
const { body } = await request("https://api.ipify.org", { dispatcher: agent });
console.log(await body.text());import { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "http://gateway.riftproxy.com:8080",
username: "USER-session-task1",
password: "PASS",
},
});curl -x http://USER:[email protected]:8080 https://api.ipify.orgErrors & limits
The gateway maps failures to standard proxy responses:
| Signal | Meaning |
|---|---|
| 407 / SOCKS auth failure | Bad credential, revoked credential, or source IP not whitelisted. |
| 403 / suspended | Balance depleted — top up to resume. Connections resume instantly on credit. |
| 502 / 503 | No healthy upstream available; the gateway retries up to 5 upstreams before failing. |
| Idle timeout | Connections idle for 10 minutes are closed. |
- Up to 5 active credentials per account.
- Unlimited concurrent sessions — pay only for bandwidth.
- Bandwidth credits never expire within 90 days.