Create your account
Sign up at zentislabs.com, verify your email with a 6-digit code, and log in to the dashboard.

This guide takes you from account creation to your first authenticated proxy request with enterprise-ready defaults. Follow the three steps below and you will be routing traffic through 100+ MIO residential IPs in under five minutes.
Sign up at zentislabs.com, verify your email with a 6-digit code, and log in to the dashboard.
Go to Settings → API Keys, create a key, and copy it somewhere safe.
Use cURL, Python, or Node.js to route traffic through a proxy pool and verify geo/IP behavior immediately.
zlk_live_# Add to your .env or secrets managerexport ZENTISLABS_API_KEY="zlk_live_a1b2c3d4e5f6..."Choose your preferred language below. Each example resolves a residential proxy in Germany and makes a test request.
# Use your proxy credentials from the dashboard# Format: http://USERNAME:PASSWORD@gate.zentislabs.com:8080curl -x "http://zl_residential_de_rotating_abc123:yourpassword@gate.zentislabs.com:8080" \ "https://httpbin.org/ip"import requests
# Use your proxy credentials from the dashboardPROXY = "http://USERNAME:PASSWORD@gate.zentislabs.com:8080"
proxies = {"http": PROXY, "https": PROXY}response = requests.get("https://httpbin.org/ip", proxies=proxies)print(f"Your proxy IP: {response.json()['origin']}")import axios from 'axios';import { HttpsProxyAgent } from 'https-proxy-agent';
// Use your proxy credentials from the dashboardconst PROXY_URL = 'http://USERNAME:PASSWORD@gate.zentislabs.com:8080';
const agent = new HttpsProxyAgent(PROXY_URL);const { data } = await axios.get('https://httpbin.org/ip', { httpsAgent: agent});console.log(`Your proxy IP: ${data.origin}`);A successful proxy resolution returns a JSON object like this:
{ "host": "gate.zentislabs.com", "port": 8080, "username": "zl_residential_de_rotating_abc123", "password": "generated-password", "protocol": "http"}Your sticky session ID. Same session = same IP for the duration of the TTL.
Time-to-live in seconds. After TTL expires, a new IP is assigned on next request.
Proxy type: residential, isp, mobile, or datacenter.
Geo-location of the assigned proxy IP, matching your targeting request.
Cause: Invalid or expired API key
Fix: Generate a new API key from Dashboard → Settings → API Keys.
Cause: Access denied
Fix: Check that your API key is valid and has not been revoked.
Cause: Too many requests per second
Fix: Implement exponential backoff. Consider upgrading your plan for higher rate limits.
Cause: No available proxies in the requested geo
Fix: Expand geo-targeting (e.g., country-level instead of city), or switch to a larger proxy pool.
Store API keys in environment variables or a secrets manager. Never hardcode keys in source code or expose them in frontend bundles.
Use exponential backoff with jitter for 429/5xx errors. Retry on a different proxy pool for the final attempt.
Track bandwidth consumption, success rates, and error rates via the dashboard or API to stay within budget and detect issues early.
Use sticky sessions for multi-step workflows (login → checkout). Use rotating sessions for high-volume scraping to maximize IP diversity.
Learn about API keys and authentication methods.
Set up pools, geo-targeting, rotation, and failover policies.
Production-ready Python, Node.js, and cURL code examples.
100M+ IPs across 195+ countries with rotating and sticky sessions.