HProxy/ docs

Your dedicated proxies

GET /api/v1/proxies lists the dedicated IPv4, IPv6, ISP and mobile proxies a key owns, credentials included — filter by family or by the order that delivered them.

GET/api/v1/proxies

List your proxies

Every dedicated proxy the account owns (IPv4, IPv6, ISP, Mobile), with connection credentials — the delivery step after a per-IP purchase. Served from a local mirror, so it's instant and keeps working through upstream turbulence: new purchases appear right after the order fulfills, everything else refreshes within ~30 minutes. Filter order_id with the id POST /orders returned to fetch exactly that order's proxies. Each proxy's id is what a renewal references in fulfillment_meta.ids.
ParameterTypeRequiredDescription
familystring (query)optional"ipv4", "ipv6", "isp" or "mobile". Omitted = all.
order_idstring (query)optionalOnly the proxies delivered by this order (ord_…).
include_inactiveboolean (query)optionaltrue to include expired/retired proxies. Default: active only.
limitinteger (query)optionalMax rows. Default 1000, max 5000.
curl "https://hproxy.com/api/v1/proxies?family=ipv4&order_id=ord_8f49...8821" \
  -H "X-API-Key: hpx_your_key_here"

Fields the record doesn't state are null, never invented. A proxy that expired or was retired flips to active: false (hidden unless include_inactive=true) — history is kept, nothing silently disappears. Residential plans don't live here: they are generated on demand from Plans & generation.

A freshly fulfilled order's proxies appear within seconds. If you get an empty list right after POST /orders, poll GET /orders/{id} until it's completed — or skip polling entirely with a webhook.

Need a hand wiring this up? Email [email protected]. A real person reads every message.