Everything you need to integrate IPLoop proxies into your workflow. API docs, code examples, and integration guides.
Step 1: Create an account or sign in at platform.iploop.io.
Step 2: Save your API key, proxy username and proxy password privately. The dashboard password, proxy password and API key are different credentials.
Step 3: Add bandwidth, then copy the HTTP and SOCKS5 endpoints from the dashboard’s Connect section. Set the values below to your own credentials and endpoints before running the examples.
PROXY_USERNAME='YOUR_PROXY_USERNAME'
PROXY_PASSWORD='YOUR_PROXY_PASSWORD'
HTTP_PROXY_ENDPOINT='COPY_HTTP_ENDPOINT_FROM_CONNECT'
SOCKS5_PROXY_ENDPOINT='COPY_SOCKS5_ENDPOINT_FROM_CONNECT'
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us:${PROXY_PASSWORD}" \
"https://api.ipify.org?format=json"
Proxy traffic: use your proxy username and proxy password. Country and session options belong in the username, not the API key or proxy password.
Dashboard: use your email and dashboard password, or choose API-key login. Keep your key private; never paste real credentials into public examples.
These instructions apply to new accounts on platform.iploop.io. Existing legacy integrations use a different key-only format and are not silently migrated by changing a URL.
Use the current endpoints shown in Connect. An HTTPS target protects the target connection; it does not by itself establish encrypted authentication to the proxy.
# HTTP CONNECT to an HTTPS target
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us:${PROXY_PASSWORD}" \
"https://example.com"
# SOCKS5 with target DNS resolved through the proxy
curl --socks5-hostname "$SOCKS5_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us:${PROXY_PASSWORD}" \
"https://api.ipify.org?format=json"
Successful connection does not guarantee that a target website will accept a request. Inspect its returned status and content.
Append an ISO alpha-2 country code to your proxy username. For example: -country-us, -country-ca, -country-gb, -country-de, -country-au or -country-tr. Availability depends on the live pool.
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-gb:${PROXY_PASSWORD}" \
"https://ipinfo.io/json"
V2 geography: State/city selectors are deployed in V2. Country is required; state is optional for a city request. Exact-city accuracy is not certified: some Austin test exits were labeled San Antonio or Schertz by independent geo services. ZIP and ASN restrictions remain unverified. Inspect observed geography when exact-city precision matters. Invalid country selectors must not be used: the backend may return an unintended geography. The V2 Python SDK validates country codes locally.
SDK 1.8.3+: client.get('https://example.com', country='US', state='tx', city='austin'). MCP: pass country, optional state and city to proxy_fetch. No feature flag is needed.
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us-state-tx-city-austin:${PROXY_PASSWORD}" \
"https://example.com"
Omit a session ID for ordinary rotating selection. Connections and pooled clients may reuse an exit; rotation does not guarantee a unique, never-used IP on every request.
# Reuse this ID for requests belonging to the same sticky session
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us-session-demo123:${PROXY_PASSWORD}" \
"https://api.ipify.org?format=json"
# Request a five-minute session (duration is in minutes)
curl --proxy "$HTTP_PROXY_ENDPOINT" \
--proxy-user "${PROXY_USERNAME}-country-us-session-demo123-sesstime-5:${PROXY_PASSWORD}" \
"https://api.ipify.org?format=json"
Use letters, digits or underscores in SDK session IDs. Change the ID to request a different session. Device availability can cause an exit change; no uninterrupted fixed-IP lifetime is guaranteed.
Use iploop-sdk 1.8.3 or newer with all three account credentials. Key-only construction retains legacy mode; it is not the new-platform example.
python -m pip install 'iploop-sdk[async,socks]>=1.8.3'
import os
from iploop import IPLoop
client = IPLoop(
api_key=os.environ['IPLOOP_API_KEY'],
proxy_username=os.environ['IPLOOP_PROXY_USERNAME'],
proxy_password=os.environ['IPLOOP_PROXY_PASSWORD'],
)
r = client.get('https://example.com', country='US', retries=2, timeout=15)
r.raise_for_status()
print(r.text)
session = client.session(session_id='my_session1', country='US', lifetime=5)
r = session.get('https://api.ipify.org?format=json', retries=1)
usage = client.usage()
print(usage['account']['balance_gb']) # decimal GB
print(usage['daily']) # daily byte counts
Set those environment variables to your own API key, proxy username and proxy password first. For synchronous SOCKS5, pass proxy_protocol='socks5h'. Async HTTP is supported through AsyncIPLoop with the same credentials and an async context manager; async SOCKS is explicitly unsupported.
V2 state/city selectors are supported from SDK 1.8.3. Rendering and country-inventory/support-message helpers remain unsupported. Unsupported helpers raise explicit errors rather than silently calling legacy services. Extractor and anti-bot results remain target-dependent.
Verified SDK release · SDK source archive
ClawHub V2 release 3.0.3 is live. New installation: clawhub install proxyclaw. Existing installation: clawhub update proxyclaw. Run bundled scripts through bash ./setup.sh and bash ./fetch.sh. Separate proxy credentials and deployed state/city selectors are supported; the exact-city accuracy caveat still applies.
The proxy platform, Python SDK and agent integrations are separate components. The updated GitHub skill supports explicit V2 proxy credentials. Older skill catalog versions may still assume legacy key-only authentication. Do not assume that installing an agent skill converts new-platform credentials automatically.
For new accounts, use the verified HTTP/SOCKS5 or Python examples above. Review each integration’s documented version and credential configuration before use.
The updated GitHub MCP source supports separate V2 proxy credentials. Clone it, run npm ci && npm run build, and configure your client to run dist/index.js. Older npm/catalog releases may remain legacy; do not assume they are updated. State/city is available by default in the updated source, with the accuracy caveat above.
401 — Account API authentication was rejected.
407 — Proxy authentication was rejected; verify the proxy credentials and syntax.
429 — Back off and respect the service response.
502 / 503 — Temporary connection/service failure; use bounded retries.
SOCKS authentication failures may appear as client connection errors instead of an HTTP code. Do not retry invalid credentials indefinitely.
The dashboard displays balance in decimal GB. The underlying account balance is bytes; usage rows also report bytes. Owner credits are separate from paid purchases. Request/success counters are service metrics, not a guarantee of successful target-site business results.
Request history is available for requests captured while account logging is enabled. Enable logging in the dashboard before a bounded diagnostic run, and turn it off when finished. An empty history view does not prove zero traffic when logging was disabled; balance and daily usage are separate views.
Our support team is available 24/7 to help you integrate IPLoop into your workflow.
Need help?
Send us your question and we’ll reply by email.
Chat is temporarily routed to email so visitors never hit a dead support widget.