Guides

Server-Side Proxy Rotation API

By the Proxy11 team. Updated .

One request returns one proxy that matches your filters, so you don't need to keep a pool in your own code. Your app still connects through that proxy itself, because this API only picks the address.

Random and sticky are selection strategies

randomsticky
PicksFrom all matching proxies on each callThe same proxy for one session label and time window
Can repeat?Yes, the same address can come up twiceYes, that is the point
Changes whenEvery callThe time window rolls over
Good forSpreading many separate requestsMulti-step flows that should keep one IP

sticky_seconds defaults to 600, and the service keeps it between 60 and 3600.

Requests

# Random: selects a matching proxy each call; repeats are possible
GET /api/rotate?key=YOUR_API_KEY&country=us&type=anonymous

# Sticky: same proxy for 10 minutes per session
GET /api/rotate?key=YOUR_API_KEY&strategy=sticky&session=scraper-1&sticky_seconds=600

# Example JSON response
{"ip":"62.255.12.3","port":"80","country":"United States",
 "country_code":"us","time":0.31,"type":1,
 "strategy":"random","session":"a1b2..."}

If you only want the address, /api/rotate.txt returns just ip:port.

The application makes the proxied request

Set the returned ip and port as your HTTP client's proxy. Use a plain label such as scraper-1 for the session, with no personal information in it. Keys are query parameters, so don't share full request URLs.


Read next