Documentation

Everything you need to go from sign-up to the first request: endpoints, authentication, targeting syntax, sessions and code samples.

Quickstart

  1. Create an account and buy traffic from 1 GB.
  2. Pick a product and country in the dashboard: it generates ready proxy lines.
  3. Plug the gateway into your tool.

The first request takes under a minute.

curl -x gate.aeonproxy.com:7000 -U "USER:PASS" https://api.ipify.org

Authentication

Login and password on every request (HTTP proxy authentication or SOCKS5 username/password). Your login starts with ap_; targeting and session keys are appended to it. Rotate the password from the dashboard at any time: the old one stops working immediately. Sub-user logins created in the dashboard work the same way, within their own traffic limit.

Endpoints & ports

ProductHostHTTP/HTTPSSOCKS5
Residentialgate.aeonproxy.com70007001
Mobilegate.aeonproxy.com70007001
ISP / Datacenterper IP, shown on the order pageper IPper IP

Residential and mobile use the same host and ports; the login you generate in the dashboard decides which pool answers.

Targeting

Append key-value pairs to the username, separated by dashes. Without a country key the exit can be anywhere.

ap_a1b2c3-cc-us                                 # country
cp_a1b2c3-cc-us-st-california                   # state or region
cp_a1b2c3-cc-us-st-newyork-city-newyork         # city, with its region
cp_a1b2c3-cc-us-isp-comcastcable                # network (residential)
cp_a1b2c3-cc-gb-st-scotland-car-three           # carrier (mobile)

Country codes are ISO 3166-1 alpha-2, lowercase (the United Kingdom is gb). Region (st), city, ISP and carrier values are the names from the dashboard's lists written as lowercase letters and digits only: “new york” is newyork, “north rhine-westphalia” is northrhinewestphalia, “comcast cable” is comcastcable. Mobile logins take car for the carrier where residential ones take isp. Region and city lists exist for every country; ISP and carrier lists for the United States, the United Kingdom and Germany so far. They need a country key. A username with an unknown key, or a value outside the lists, is rejected with 407 — it never falls back to the whole country.

How precise it is: in our October 2026 check (40 residential sessions per level, exits placed by ipinfo.io) 97% of US and 88% of German exits landed in the state or Land asked for, and 82% (US) and 92% (Germany) in the city. UK nations and cities matched less often (73% and 42%), mostly because geolocation databases place many UK addresses in London. ISP and carrier matched in 95–100% of sessions. Check the exit with the IP checker when the location matters.

Sessions & rotation

Without a session key every connection exits from a new IP. To keep an IP, add sid with any key of letters and digits: all connections with the same key share one exit. ttl sets how many minutes the exit is kept, 1–60 (10 when omitted); after that the key moves to a new IP.

ap_a1b2c3-cc-gb-sid-abc12345
cp_a1b2c3-cc-gb-sid-abc12345-ttl-30   # minutes, max 60

The dashboard generates lists of such usernames with a fresh key per line, so each line is its own sticky session.

Protocols

HTTP and HTTPS (CONNECT) on port 7000; SOCKS5 with username/password auth on port 7001, including UDP (UDP ASSOCIATE: the gateway relays your datagrams through the same exit IP, so QUIC, DNS and other UDP traffic work) for residential and mobile. ISP and datacenter proxies additionally support p0f OS profile switching from the dashboard.

Code examples

import requests
proxy = "http://ap_a1b2c3-cc-us-st-texas-city-dallas:[email protected]:7000"
r = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=15)
print(r.text)

Limits & fair use

Unlimited concurrent threads on all plans; traffic is metered per login and per sub-user. Per-IP products have a fair-use policy against abuse. Accessing resources prohibited by law or by our terms is blocked at the gateway, and so are some targets by default: mail ports, government and military sites, and some banking and ticketing sites (Acceptable Use Policy, section 4).

Errors

CodeMeaningWhat to do
407Bad credentials or unknown username keyCheck the login, password and the keys appended to the login
403Target blocked by default (the X-Reason header says why)Pick another target, or ask support for access after identity verification
402No traffic left on the plan or the sub-user limitBuy traffic or raise the sub-user limit in the dashboard
502Exit failedRetry; a rotating login picks another exit, a sticky one keeps its key

Questions? Ask support in the live chat.