Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

Change a proxy IP by link: how rotation links work

A rotation link for one sticky proxy session: the link is created once with the API, then opening it restarts the session; in our test 3 calls of the link gave 3 new exits, with a 10 second pause between rotations.
A rotation link for one sticky proxy session: the link is created once with the API, then opening it restarts the session; in our test 3 calls of the link gave 3 new exits, with a 10 second pause between rotations.

To change a proxy IP by link, create a rotation link for a sticky session and open it whenever you want to restart the session. The link restarts that one session, and the next request with the same string is assigned an exit again; in our run that was a new IP each of three times. On QuanticData rotation links are available on Residential Basic and traffic-based Datacenter plans, and the link needs no API key.

We ran the whole cycle on 20 November 2026 on a Residential Basic plan, the one tested for this post: create a link, call it three times, list it, revoke it. Every request and answer below is from that run, with ids, tokens and exit addresses replaced by placeholders.

A sticky proxy string carries a session name in its username. A sticky string asks the gateway to keep requests on one exit; in our run four requests in a row showed the same address. A rotation link is a URL tied to that session name. Opening it tells the gateway to start the session again, and the next request made with the same string is assigned an exit again.

That is why people ask for it for antidetect browser profiles and long-running scripts: host, port, username and password in the tool stay as they are, and a click or one HTTP request restarts the session. Nothing has to be pasted again.

You haveYou doResult
A sticky string in a browser profile or a scriptCreate one rotation link for it, onceA URL to keep next to the profile
The URLOpen it in a browser, or call it with curlThe session restarts
The same sticky stringSend the next requestThe session's next exit (new in 3 of 3 calls in our run)

Step 1: get a sticky string

Rotation links belong to sticky sessions, so start from a sticky string. The dashboard generator writes one, and so does the API. The orderId of your plan comes from GET /public/proxies.

curl -s -X POST https://api.quanticdata.io/v1/public/proxies/generate \
  -H "Authorization: Bearer $QD_API_KEY" -H "Content-Type: application/json" \
  -d '{"orderId":"ORDER_ID","country":"us","rotation":"sticky","sessionTime":30,"quantity":1,"format":"http://user:pass@host:port"}'

The string that came back had this shape, with the session name and its length in the username:

http://USER-type-residential-country-us-session-SESSION_ID-lifetime-30:PASS@residentialboson.quanticdata.io:10000

Before rotating we sent four requests through it to an IP echo service: the same exit answered on 4 of 4.

Send the sticky string to the rotation-links endpoint of the plan. A label is optional and helps when you keep one link per profile.

curl -s -X POST https://api.quanticdata.io/v1/public/proxies/ORDER_ID/rotation-links \
  -H "Authorization: Bearer $QD_API_KEY" -H "Content-Type: application/json" \
  -d '{"proxy":"http://USER-...-session-SESSION_ID-lifetime-30:PASS@residentialboson.quanticdata.io:10000","label":"Profile 12"}'

The answer in our run, status 201:

{"type":"response","message":"Rotation links created. Save each url now: it is not shown again.",
 "payload":{"orderId":"ORDER_ID","links":[{"id":"rlk_LINK_ID","sessionId":"SESSION_ID","port":10000,
   "protocol":"http","label":"Profile 12","tokenHint":"a1b2","useCount":0,"revoked":false,
   "url":"https://api.quanticdata.io/v1/public/rotate/rl_TOKEN","token":"rl_TOKEN"}]}}

Copy the url at once. Only a hash of the token is stored, so later listings show the last four characters (tokenHint) and nothing more. One call accepts a single string in proxy or up to 100 in proxies, one link per string, and a plan can hold up to 1,000 active links.

The link takes no API key, no header and no body. A browser tab, a bookmark or the "change IP URL" field of an antidetect browser can call it as it is.

$ curl -s https://api.quanticdata.io/v1/public/rotate/rl_TOKEN
{"type":"response","message":"Session rotated. The next request on this proxy string gets a new IP.",
 "payload":{"rotated":true,"sessionId":"SESSION_ID","port":10000,"protocol":"http",
   "rotatedAt":"2026-11-20T18:20:51.752Z","nextAllowedAt":"2026-11-20T18:21:01.752Z",
   "linkId":"rlk_LINK_ID","label":"Profile 12"}}

We called the link three times, eleven seconds apart, and read the exit twice after each call with the unchanged proxy string. Each call was followed by a new exit, three new exits in three calls, and both reads after a call showed the same address.

$ curl -s -x "$STICKY_STRING" https://ipinfo.io/ip
x.x.x.x        # after call 1, twice the same
x.x.x.x        # after call 2, a different exit, twice the same
x.x.x.x        # after call 3, a different exit, twice the same

Wait for the 200 before you send the next request through the proxy, so that the request lands on the restarted session.

The 10-second pause, and other limits

A session can be rotated once every 10 seconds. The answer to a rotation says when the next one is allowed (nextAllowedAt). When we called the link again straight away in this test, it answered 429 with a Retry-After header of 8 seconds:

{"type":"error","message":"This session was rotated less than 10 seconds ago. Try again in 8 s.",
 "payload":{"code":"RATE_LIMITED","scope":"session","retryAfter":8}}
  • Per session: one rotation every 10 seconds.
  • Per account: 1,200 rotations an hour, shared between links and the rotate endpoint.
  • Per plan: up to 1,000 active links.
  • HEAD requests answer 405 and do not rotate, so a link preview in a chat app does not change your IP.

A script that gets the 429 should wait the seconds in Retry-After and call once more. The general pattern is in 429 Too Many Requests.

Treat the URL like a password for that one session. It cannot read credentials or spend balance; it can only restart the session it was made for. If a link leaks or a profile is retired, revoke it.

# list: ids, labels, use counts, last four characters of each token
curl -s https://api.quanticdata.io/v1/public/proxies/ORDER_ID/rotation-links -H "Authorization: Bearer $QD_API_KEY"

# revoke one
curl -s -X DELETE https://api.quanticdata.io/v1/public/proxies/ORDER_ID/rotation-links/rlk_LINK_ID -H "Authorization: Bearer $QD_API_KEY"

In our run the listing showed "useCount":3 for the link, with the limits of the plan ("activeLinksPerPlan":1000,"cooldownSeconds":10). After the revoke, the link answered 410 with the code LINK_REVOKED and the message "This rotation link was revoked. Create a new one for this session."

A script that already holds the API key does not need a link. POST /public/proxies/ORDER_ID/rotate with the sticky string in proxy restarts the session the same way and shares the same limits. The link exists for places where a key should not be stored: a browser profile, a teammate's bookmark, a no-code tool.

Mobile and Residential Premium: a new string is a new session

On mobile proxies and on Residential Premium each sticky string is its own session, named in the username: for a new exit, ask generate for a new sticky string, which comes with a new session name. On our Mobile plan, three sticky strings requested in one call exited from three different addresses, and each string showed the same exit on two requests in a row. On our Residential Premium plan the same test gave the same result: three strings, three exits, each the same over two requests. ISP plans are dedicated static IPs.

For the difference between rotating and sticky strings, see how to use rotating proxies; proxy syntax for curl is in how to use a proxy with curl. Every endpoint used here is in the API reference, under Proxies. Rotation links come with residential proxies on the Basic pool and with traffic-based datacenter proxies.

Sources & further reading

FAQ

Quick answers on change IP by link.

Something else? Ask us

How do I change my proxy IP by link?

Create a rotation link for your sticky proxy string with POST /public/proxies/ORDER_ID/rotation-links, save the URL from the answer, and open it whenever you want to restart the session. In our run the same string exited from a new address after each of three calls.

Does the rotation link need an API key?

No. Creating, listing and revoking links needs the API key; calling the link does not. It takes no header and no body, so a browser, a bookmark or an antidetect browser can open it.

How often can I rotate a session?

Once every 10 seconds per session, and 1,200 rotations an hour per account. A call that comes too early answers 429 with a Retry-After header; in our test it said 8 seconds.

Do I have to change the proxy settings after rotating?

No. Host, port, username and password stay the same. In our run the unchanged string exited from a new address after each of three link calls.

Is there a change-IP link for mobile proxies?

On Mobile and Residential Premium each sticky string is its own session, so a new session comes from a new string: call POST /public/proxies/generate again. In our test three new strings on the Mobile plan exited from three different addresses.

What happens if someone else gets my rotation link?

They could restart that one session and nothing else: the link carries no credentials and cannot spend balance. Revoke it with DELETE /public/proxies/ORDER_ID/rotation-links/LINK_ID; a revoked link answers 410.

Restart a session with one link

Residential Basic plans include rotation links: one URL per sticky session, no key in the link, revocable at any time.

Related reading