How to Use Long Session IDs (NNID) for Rotating Residential Proxies

This guide will help you set up and use the Long Session ID feature (NNID) with rotating residential proxies, ensuring stable IP sessions for extended use. With Long Session IDs, you can maintain the same IP address for up to 30 Minutes, which can be beneficial for applications requiring a longer session duration.
Note:  State and City shall be left on Random if you wish to use Long Session ID. 
SOCK5 can only be used after receiving long session token

Step 1: Understanding the Long Session ID (NNID) Feature

The Long Session ID (NNID) feature allows you to keep the same IP address for longer than a standard session, making it ideal for tasks that need consistent IPs without frequent rotation. This guide uses the nnid-0 parameter, which will hold the IP for up to 30 minutes.

Step 2: Get the Curl Link 

Extract the Curl Link from the admin panel dashboard as shown below and adjust it as shown in Step 3. 

Step 3: Setting Up the Command with Your Details

To use the Long Session ID feature, your cURL command must include resfix, and the nnid-0 parameter.

Open the Command prompt by Pressing the Windows Key + R to open the Run dialog box.

Type CMD and press Enter. This will open the Command Prompt where the curl link needs to be pasted and amended.

Copy the cURL link extracted from the dashboard ( shown in step 2 ) and paste it into the Command Prompt window.

Make Necessary Replacements:

• Replace res with resfix to specify a fixed residential IP.
• Ensure nnid-0 is included (replace whatever appears after nnid- with 0).
• Update <country> with your desired country code you can select any country from the list during generating credential. 

If everything is done accordingly it should look something like this: curl -v -x http://pctMLxol7j-resfix-us-nnid-0:[email protected]:5959 https://ipv4.icanhazip.com

Step 4: Retrieve the Unique Token for Persistent IP

After running the  command shown above, you’ll receive a response that includes a header( X-NN-LLS) as shown below. This unique token (34c6c386e136f7f2a0f1 in this example) allows you to keep the same IP for multiple requests.

Step 5: Use the Unique Token for Subsequent Requests

To maintain the same IP across multiple requests, replace nnid-0 with nnid-<unique token>as shown below: 

Step 6: Run the Command with unique token

• The unique token is specific to the initial country you selected. For instance, if you initially selected a UK IP, then using the token will maintain a UK IP for the session.
• Refreshing the IP: Each time you want a new IP address, revert to nnid-0 to generate a fresh unique token. This will assign a new IP based on your country choice and start a new session.
•