A REST API for proxy management, IP changes and usage statistics is planned. Join the waitlist and tell us what you need.
Until the API is available, access is configured with standard proxy credentials. Any client that supports HTTP(S) or SOCKS5 proxies can use them.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://example.com/import requests
proxy = "http://USERNAME:PASSWORD@HOST:PORT"
r = requests.get("https://example.com",
proxies={"http": proxy, "https": proxy},
timeout=15)
print(r.status_code)Two read-only endpoints work without an account: the ones our own status page and IP checker call. They return JSON and store nothing.
GET /api/health returns the state of the API and its database. A 503 with degraded means the database did not answer.curl https://xameleon.cloud/api/health{"status":"ok","db":"ok","time":"2026-10-08T12:00:00.000Z"}GET /api/tools/ip returns the address and the country our server sees for the request. Send it through a proxy to see the exit IP. Up to 30 requests per minute per address; nothing is stored.curl -x http://USERNAME:PASSWORD@HOST:PORT \
https://xameleon.cloud/api/tools/ip{"ip":"203.0.113.25","country":"UA"}/api/health and /api/tools/ip. The management API for proxies and IP changes is planned.Describe the integration you have in mind and our team will get back to you.
A proxy management API would let your own systems handle proxy access, IP changes and usage numbers without manual steps. The Xameleon mobile proxy API is planned, not released. There is no release date yet, and we will publish the details on this page before launch.
The waitlist form on this page asks only for your e-mail, and we use it for one message: the announcement that the API is ready. If you have a specific integration in mind, describe it to our team. Early access is on request, and we are already in contact with the first integrators.
The planned proxy management API has four areas: managing proxy access, changing the IP, showing how much traffic and how many requests you use, and connecting Xameleon with your own tools. These are goals, not finished features, and details can change before launch. API access is planned for enterprise and reseller plans, and the mobile proxy solutions page explains how to ask about timing.
When the service launches, you connect with the details every proxy client understands: host, port, and a username and password. That works with curl, Python requests, browsers and scraping frameworks that speak HTTP(S) or SOCKS5. The guide on how to use mobile proxies shows the connection step by step, and the Python proxy tutorial adds code for sessions, timeouts and retries.
You do not need the API to automate everyday work. Your IP stays the same while you work, you change it from your account, and your own client can retry, pace requests and switch between several proxies as needed. The guide to rotating proxies automatically shows how to rotate between proxies in your own code. To see what a setup involves, compare plans and per-country prices.
To help us plan, describe the job you want the API to do: creating proxy access, rotating IPs from your own code, reporting usage to your clients or something else. Questions go to [email protected] or Telegram. While you wait, the documentation lists the guides and free tools that already exist.