API & Usage Docs
Everything you need to start using ProxyAsap shared US HTTP proxies. Your list is delivered instantly after payment and works with any tool that speaks standard HTTP proxying — curl, Python, browsers and desktop software.
Credentials format
Every proxy in your service uses one shared login and password. Lines follow a single, predictable layout so you can paste them straight into any tool.
Each line in your list is formatted as:
A real line looks like this (values below are illustrative — use the ones from your own service):
LOGIN and PASSWORD are the same across every IP in one service — one shared login per service. Only the IP (and sometimes the PORT) changes from line to line. Keep these credentials private; anyone who has them can use your proxies.
Grab your current list any time from the service page in your dashboard.
HTTP proxy usage (curl)
ProxyAsap proxies speak the standard HTTP proxy protocol, so the built-in -x flag in curl is all you need. It works for both plain HTTP and HTTPS targets.
Send a request through one proxy and print the exit IP:
With real-looking values:
If api.ipify.org returns the proxy IP instead of your own, the proxy is working. You can also set the http_proxy and https_proxy environment variables so every command inherits the proxy without the -x flag.
Python (requests)
In Python, pass a proxies dictionary to the requests library. The same URL format — login, password, IP and port — applies.
To rotate across your pool, load the lines from your list, split each on : into IP, port, login and password, and pick a different entry per request. A short timeout plus a retry on the next line keeps a batch job moving.
Browser & software setup
Any application with an HTTP proxy field works. The pattern is always the same: host, port, then the login and password when prompted.
Select HTTP as the proxy type everywhere — these are HTTP proxies. HTTPS targets are tunneled over the same HTTP proxy connection automatically.
Authentication
Access is granted by username and password — the standard user:pass proxy authentication scheme.
Every request must carry your LOGIN and PASSWORD. In a URL they go before the host, separated by a colon and an @ sign:
One shared login covers the whole service, so you use the same pair for every IP in your list. There is no separate API key or token — the proxy login is the credential. If you ever need to change it, contact support.
Getting your list
Your proxies are ready the moment payment clears — nothing to configure on our side first.
Rotation & sessions
These are shared US HTTP proxies delivered as a fixed list of IPs. Rotation is handled by your own code — you choose which line to use for each request or session.
List-based rotation. Each line is a distinct IP that stays the same for as long as it is in your list. To rotate, iterate through the lines and switch to the next IP whenever you want a fresh exit address.
Sticky sessions. Keep the same IP for a whole login or checkout flow by reusing one line for all requests in that session, then move to a different line for the next one.
Concurrency. Because the pool is shared, spread your traffic across several lines rather than hammering a single IP — it is gentler on targets and reduces rate-limit hits.