# Proxare API — complete integration guide This file is written for an AI assistant or a developer who wants to integrate Proxare quickly. Everything needed is here; no other page has to be read. Machine-readable version: https://www.proxare.com/v1/openapi/ ## What Proxare is Proxare resells residential, mobile and ISP (static residential) proxies. A customer buys GB (or IPs for ISP), and gets one proxy login per product. Traffic is billed per GB; bought GB stay valid for 365 days. Product ids used everywhere in the API: - `oxylabs` — Oxylabs, from $2.49/GB - `decodo` — Decodo, from $2.39/GB - `brightdata` — Bright Data, from $2.29/GB - `iproyal` — IPRoyal, from $1.99/GB - `private` — Proxare Premium, from $1.79/GB - `basic` — Proxare Standard, from $0.89/GB - `geonode` — Geonode, from $1.49/GB - `packetstream` — Packetstream, from $1.49/GB - `mobile` — Proxare Mobile, from $1.49/GB - `isp` — ISP proxies (static residential), from $1.49 per IP per month ## Authentication Every call that touches an account needs an API key, made by the customer at https://www.proxare.com/dashboard/ under Settings -> API keys. The key looks like `pxr_live_` followed by 40 characters and is shown only once. Authorization: Bearer pxr_live_7Kq2xR4mNvB8cTfW1yZp6LdJhA3sEgU9nQ0rXiOk Keys carry scopes: `read` (account, orders, countries), `generate` (proxy lists), `manage` (whitelist, password reset). New keys have all three. A key is not tied to an IP, so desktop software can use it directly; the API sends `Access-Control-Allow-Origin: *`, so a browser extension can too. Rate limit: 120 requests a minute per account, answered with HTTP 429. Treat a key and a proxy login like passwords. Do not write them to logs, do not paste them into a chat transcript, and do not show them to anyone but the customer who owns them. ## Endpoints Base URL: https://www.proxare.com/v1/ — all answers are JSON. Keep the trailing slash. ### GET /v1/products/ (no key) Products, pack sizes and prices. Use it to show a price before the customer has an account. ### GET /v1/account/ The account: email, the key's scopes, total GB left, and one entry per product owned with `username`, `limitGb`, `usedGb`, `leftGb`, `whitelist`, `canWhitelist`, `canResetPassword`. If a product's network cannot be reached, that entry has an `error` string instead of numbers; the rest of the answer is still good. ### GET /v1/subaccounts/ The same products, trimmed to `id`, `name`, `type`, `username`, `leftGb`, `usedGb`, `limitGb`. This is what fills a "sub-account" dropdown. ### GET /v1/countries/?product= Countries that can be targeted. For `product=mobile` it returns the live list with carriers. For everything else it returns the common codes; any ISO 3166-1 alpha-2 code the network supports also works. ### GET /v1/orders/ Paid orders: product, quantity, USD amount, status, dates. ### POST /v1/proxies/ <- the important one Generates proxy lines from the customer's own login. Free, unmetered, instant. Request body: { "product": "private", // required, a product the account owns "count": 100, // 1-1000, default 10 "country": "de", // two letters; leave out for any country "countries": ["us","de"],// or several: the list is spread over them, one per line in turn "mixed": false, // true spreads over the standard pool of 19 countries "city": "", // optional, with a country, e.g. "new_york" "carrier": "", // mobile only, code from /countries/?product=mobile "sticky": true, // true: one IP per line for `lifetime`; false: a new IP every request "lifetime": "30m", // 10m | 30m | 1h "protocol": "http", // http | socks "format": "hpup", // hpup | uphp | uphp2 | url "region": "auto" // auto | eu | asia — which gateway to connect to, not the exit country } Answer: { "product": "private", "name": "Proxare Premium", "count": 100, "host": "premium.proxare.com", "port": 6011, "scheme": "http", "username": "px_alice", "rotating": false, "countries": ["de"], "format": "hpup", "leftGb": 43.812, "usedGb": 6.188, "proxies": ["premium.proxare.com:6011:px_alice:k7Qm2x-country-de_session-ab12cd34_lifetime-30m", "..."] } Write `proxies` straight into a proxy list file. A GET form with the same parameters in the query string exists for tools that cannot POST; those may also pass `?api_key=...` instead of the header. ### POST /v1/whitelist/ (scope: manage) `{"ips": ["203.0.113.10"]}` — up to 10 public IPv4 addresses, which may then connect without a password. The list sent replaces the old one. Add `"product"` to limit it to one product. ### POST /v1/password/ (scope: manage) `{"product": "private"}` — makes a new 8-character proxy password and returns it once. Proxy lists built with the old password stop working, so only do this when the customer asks. ## Proxy line formats The same line in each `format`, for a sticky US session: hpup premium.proxare.com:6011:px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m uphp px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m@premium.proxare.com:6011 uphp2 px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m:premium.proxare.com:6011 url http://px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m@premium.proxare.com:6011 `hpup` (host:port:user:pass) is what most proxy managers import. A rotating line has no session id: premium.proxare.com:6011:px_alice:k7Qm2x-country-us Targeting is carried in the credentials, not in the host: the suffix after the password (after the username for Geonode) says country, city, session and lifetime. Do not build these strings by hand — ask the API for them. ## Errors Every failure is JSON with a human-readable `error` and a short `code`: no_key 401 missing, unknown or revoked key scope 403 the key lacks read / generate / manage product 400 unknown product id country 400 not a two-letter code not_owned 404 the account does not own that product no_password 409 no proxy password yet; call /v1/password/ first upstream 502 the proxy network could not be reached; retry not_found 404 no such endpoint Show `error` to the user as it is: the wording is meant for people. ## MCP server https://www.proxare.com/mcp/ — Streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18. Configuration: { "mcpServers": { "proxare": { "type": "http", "url": "https://www.proxare.com/mcp/", "headers": { "Authorization": "Bearer pxr_live_..." } } } } Tools, with what they need: list_products no key products and prices price_quote no key what a pack costs buy_link no key a checkout URL for the person to open setup_guide no key setup steps for AdsPower, Dolphin Anty, ScrapeBox, Scrapy, Puppeteer my_account read products owned, GB used and left list_orders read paid orders list_countries read countries and mobile carriers generate_proxies generate a proxy list from the account's own login whitelist_ips manage replace the IP whitelist reset_proxy_password manage new proxy password Without a key the server still answers the four public tools, so prices can be compared before signing up. ## Recipes Add a Proxare tab to a proxy manager or bot — three calls: 1. GET /v1/subaccounts/ -> fill the sub-account dropdown, show "GB left" 2. GET /v1/countries/ -> fill the country dropdown 3. POST /v1/proxies/ -> write `proxies` into the tool's proxy list file Python: import requests r = requests.post("https://www.proxare.com/v1/proxies/", headers={"Authorization": f"Bearer {KEY}"}, json={"product": "private", "count": 50, "country": "us"}) proxies = r.json()["proxies"] Node: const r = await fetch("https://www.proxare.com/v1/proxies/", { method: "POST", headers: { Authorization: `Bearer ${KEY}`, "Content-Type": "application/json" }, body: JSON.stringify({ product: "private", count: 50, country: "us", format: "url" }), }); const { proxies } = await r.json(); Using one line with curl: curl -x "http://px_alice:k7Qm2x-country-us_session-ab12cd34_lifetime-30m@premium.proxare.com:6011" https://api.ipify.org ## Things that are easy to get wrong - Generating costs nothing. Never ration calls to /v1/proxies/ or cache lines to "save GB". - `leftGb: 0` does not make generation fail; the proxies simply will not connect until the customer tops up. Show a warning, do not block the button. - One line = one session = one IP. For 100 different IPs ask for `count: 100`, do not reuse one line. - `region` picks the gateway you connect to, for latency. `country` picks the exit IP. They are not the same. - Geonode puts the targeting options on the username and uses a separate sticky port; the API handles that. - ISP proxies are real IPs delivered per order, not a gateway: /v1/proxies/ with `product: "isp"` returns the IPs already bought, and `count` only trims that list. - Buying is not in the API. Send the customer to https://www.proxare.com/checkout/ or use the MCP tool `buy_link`. ## Support Telegram @quantaccount, or https://www.proxare.com/contact/. Partner integrations (a built-in Proxare tab, revenue share): https://www.proxare.com/contact/