X
X
10% off your first order! Use coupon code WELCOME at checkout.

Mobile Proxy API Key and IP Reset Link: Location, Triggering and Automation

HomepageKnowledge BaseProxyMobile Proxy API Key and IP Reset L...
Knowledge Base 392
Mobil Proxy paketlerini ve fiyatlarını inceleyin Paketleri Görüntüle

In the Mobile Proxy service, the API key and the IP reset link let you perform IP changes and other proxy management operations through software, scripts and automation tools. This article explains where the API key and IP reset link are located, how to trigger them, automation examples, security recommendations and common issues.

What Are the API Key and the IP Reset Link?

  • IP Reset Link (IP Reset URL): A service-specific link. Sending an HTTP GET request to it renews the current IP address of the Mobile Proxy.
  • API Key: A unique authentication key that provides programmatic access to the service. In addition to IP changes, status, quota and settings operations can also be performed via the API.

Main uses:

  • Changing the IP without logging in to the panel
  • Integration with bots, automation tools and your own software
  • Repeating the same operation across multiple services with scripts
  • Querying service status and remaining quota

Who Can Use It, and Is It Paid?

API access is not limited to reseller accounts. Every customer with a Mobile Proxy service can view the API key and the IP reset link in the client area. No separate application or account upgrade is needed; API access comes with the service and is not charged separately.

Where Are the API Key and the IP Reset Link?

  1. Log in to the livaproxy.com client area.
  2. Open the detail (product management) page of the relevant Mobile Proxy service under My Services.
  3. The page shows the IP reset link and the API key; they can be copied using the copy icon.
  4. The list of available API operations and usage notes is in the "API" section on the same page.

The proxy connection details (server, port, username and password) are also on the same page. There is no need to build the link manually; the link provided in the panel should be copied and used as is.

How Is the IP Reset Link Triggered?

Sending an HTTP GET request to the link is enough. In the examples below, replace RESET_BAGLANTINIZ with the IP reset link copied from the client area.

Web Browser

Pasting the link into the browser's address bar and opening it starts the IP change.

cURL (Command Line)

curl "RESET_BAGLANTINIZ"

Python

import requests

reset_url = "RESET_BAGLANTINIZ"
response = requests.get(reset_url)
print(response.text)

JavaScript (Node.js)

fetch('RESET_BAGLANTINIZ')
  .then(response => response.text())
  .then(data => console.log(data));

PHP

$reset_url = "RESET_BAGLANTINIZ";
$response = file_get_contents($reset_url);
echo $response;

Bots and Automation Tools

Many bots and automation tools provide an "IP Reset URL" or "Rotation URL" field. Pasting the full link copied from the panel into this field is enough; the tool sends a request to the link whenever it needs to change the IP.

The result is returned in the response body; logging the response makes it easier to track errors.

Points to Consider During IP Reset

  • Send the request over a direct connection: It is recommended to send the reset request over your direct internet connection rather than through the proxy. Because the proxy connection is re-established during the IP change, a request sent through the proxy may not receive a response. If all traffic is routed through the proxy, the reset request may fail; in bots and automation tools, a "direct connection" or "bypass proxy" setting can be used for the reset request.
  • Waiting time: The IP change may take a few seconds to complete. Waiting briefly after the reset request before opening a new connection is recommended.
  • Connection drops: Active connections may be interrupted during the IP change; your application should be designed to reconnect.
  • Excessive resets: It is recommended not to send a new reset request before the previous one completes, and not to send requests back to back at very short intervals.

Checking the IP After a Reset

  • The new IP can be seen by sending a request to https://api.ipify.org through the proxy.
  • IP changes can be tracked in the "IP History" section on the service detail page.
  • The status of the operation can be monitored by checking the response to the reset request.

Automation Scenarios and Usage Examples

Time-Based Automatic IP Change

The most practical way to change the IP at regular intervals is the Auto Rotation setting in the client area. The interval is entered in seconds; it can be set to a minimum of 120 seconds, and entering 0 turns the feature off. The same can be done with a cron job or scheduled task:

Linux Cron Example (every 5 minutes):

*/5 * * * * curl "RESET_BAGLANTINIZ"

IP Rotation Based on Request Count

import time
import requests

reset_url = "RESET_BAGLANTINIZ"
requests_count = 0
max_requests = 100

for i in range(1000):
    # Your operations here
    requests_count += 1

    if requests_count >= max_requests:
        requests.get(reset_url)
        requests_count = 0
        time.sleep(5)  # wait for the IP change

Automatic IP Change on Errors

Example of changing the IP and retrying when a website returns a block (403/429):

import time
import requests

def make_request_with_auto_reset(url, proxy, reset_url):
    try:
        response = requests.get(url, proxies=proxy, timeout=10)
        if response.status_code in (403, 429):
            # Blocked, change IP
            requests.get(reset_url)
            time.sleep(5)
            # Retry
            return requests.get(url, proxies=proxy)
        return response
    except Exception:
        # Connection error, change IP
        requests.get(reset_url)
        time.sleep(5)
        return None

Other API Operations

Besides IP reset, the "API" section of the client area lists other operations:

  • Reboot: Restarting the proxy device
  • Proxy Info: Querying service and connection details
  • Quota Check: Finding out the remaining data quota
  • IP History: Listing previously assigned IP addresses
  • Uptime Status: Querying the service's operating status
  • Auto Rotation, Username/Password, IP Whitelist, TCP Fingerprint OS: Changing the related settings

How to use each operation and the required parameters are explained in the "API" section on the service detail page in the client area.

Security and Best Practices

The API key and the IP reset link are credentials that allow operations on the service:

  • They should not be shared with third parties or left in source code in public repositories (GitHub, etc.)
  • They should be stored in environment variables or a secure password manager
  • .env files should be added to .gitignore when pushing code to version control
  • API responses can be logged to track errors
  • If the key or link is suspected to have fallen into someone else's hands, the situation should be reported by creating a support ticket

Common Issues and Solutions

The API key appears to be invalid

Copy the key using the copy icon in the client area; if copying manually, make sure no spaces or invisible characters are added.

The IP reset does not work

  • Check that the link was copied in full from the panel and exactly matches the current link there.
  • If the proxy username or password was changed, copy the current link from the panel again.
  • Make sure the reset request is sent over the direct internet connection, not through the proxy.
  • Check on the service detail page that the service is active and the quota has not run out.
  • Wait briefly and try again.

The connection cannot be established right after a reset

Wait a few seconds for the IP change to complete, then reopen the connection.

Technical Support

For API-related issues, a support ticket can be created in the client area, or contact can be made via WhatsApp (0850 309 48 10). Including the error message received and the programming language or bot/automation tool used in the ticket helps resolve the issue faster.

Start small

Try the smallest package

Test your use case with a single package first and scale up once you are happy.

Powered by WISECP
Top