IP rotation is one of the key reasons to use mobile proxies. The ability to change the address exactly when you need it — before a session starts, after a series of actions or on a schedule — gives control that neither datacenter nor residential P2P pools have. In this article we break down how API rotation works, how to set it up, how to verify the change actually happened, and which mistakes most often break the integration.

Types of IP rotation

Before configuring, you need to understand the two address-change modes.

On-demand rotation

You hit a special API link or endpoint, and the carrier assigns a new public IP to the SIM card. This is the most controlled option: the change happens exactly when you need it, not on a timer.

Timer-based rotation (auto)

The IP changes automatically after a set interval — for example, every N minutes. Convenient for background tasks, but less precise for account scenarios where the change is better tied to application logic.

How rotation works on a mobile proxy

Mobile proxies from turbon.rent are built on physical SIMs of real carriers in 17 countries via GoIP/Simpool infrastructure. The IP change is implemented at the carrier session level.

What happens under the hood

  • The API command triggers a re-establishment of the mobile data session on the SIM.
  • The carrier issues a new public IP within the same telecom ASN.
  • Geolocation and carrier are preserved — only the address itself changes.
  • The old IP is released back into the carrier's CGNAT pool.

Step-by-step rotation setup via API

Step 1. Get the key and endpoint

In your dashboard take the access token and rotation URL bound to a specific proxy port. Never publish this key — it controls your channel.

Step 2. Lock access by IP (whitelist)

Where possible, restrict the rotation API call to an allowlist of your server's IPs. This protects the key from outside use even if it leaks.

Step 3. Build the HTTP request

Rotation is usually triggered by a simple GET or POST request to the issued URL with the token. Example logic in pseudocode:

  • GET to the rotation URL with your token.
  • Wait for a success response (HTTP 200 and a body with status).
  • Hold a short pause — the mobile session needs a few seconds to re-establish.

Step 4. Verify the IP actually changed

Right after rotation, request the external IP through the proxy (any "what is my IP" service or your own endpoint) and compare it with the previous one. The address should differ but stay in the same country and on the same carrier.

Step 5. Tie rotation to application logic

Best practice is to change the IP not blindly on a timer, but at task boundaries: before a new account session starts, after a series of actions, or at the first signs of rate limiting.

Embedding rotation into an antidetect environment

If you work through an antidetect browser with separate profiles, tie the rotation call to the profile lifecycle.

  • One profile — one proxy port — one telecom channel.
  • Call rotation between profile sessions, not in the middle of active account work.
  • After rotation, check consistency: IP, timezone, language and DNS should point to one country.

Common setup mistakes

Triggering rotation too often

Changing the IP every few seconds looks unnatural and becomes an anomaly signal itself. Rotate by task logic, not in an endless loop.

Not verifying the change result

If you don't recheck the IP after the call, you can work on the old address thinking rotation succeeded. Always confirm the change with an external IP request.

Ignoring a geo or ASN change

If after rotation the address "jumps" to another country or another ASN, it breaks the fingerprint. Quality mobile rotation keeps the carrier and geolocation.

Storing the rotation key in plain text

The rotation token equals control over the channel. Keep it in secrets, not in client code, and restrict it by IP.

Frequently asked questions

How long does an IP change take?

Usually from a few to a dozen seconds: the mobile data session needs to re-establish with the carrier. So after the call it's worth holding a short pause before checking.

Will the same carrier and country remain after rotation?

Yes. Proper rotation on a physical SIM changes only the public IP within the same telecom ASN, preserving country and carrier. This matters for fingerprint consistency.

Can rotation be automated on a schedule?

Yes, but for account scenarios on-demand rotation tied to task logic is preferable to a blind timer. Both options are available via API.

Bottom line: API rotation is about control, not chaos. Take the key, lock access by IP, change the address at task boundaries and always verify the result. For managed rotation on physical SIMs connect mobile proxies from turbon.rent, and for account registration on clean numbers use OTP activations from turbon.rent.