Integrations

Tools and Setups We Have Tested on New York Lines

A line from us is a host, two ports, a username and a password, plus a VLESS link. Almost everything that speaks HTTP or SOCKS5 can use it. Below are the tools our customers actually use, in the order we would reach for them, with the settings that matter on a New York carrier address. Nothing here is a paid placement; it is what we have set up ourselves and know works.

Undetectable.io

Antidetect browser

Our first pick for separate browser profiles on separate lines. SOCKS5 with DNS through the proxy, time zone from IP, one profile per line.

Create a profile named after the line, for example NYC-VZ-01.
Choose SOCKS5, enter host, SOCKS5 port, username and password from the dashboard.
Set time zone and geolocation to follow the IP; language en-US; WebRTC through the proxy.
Press the proxy check and confirm the carrier and New York before launching.

Close the profile before you rotate, then relaunch; rotating under an open profile drops its sessions.
Do not attach two account profiles to one line; they would share an address.

GoLogin

Antidetect browser

Second pick, with a built-in proxy manager and a cloud mode that still exits through your New York line.

Add the line in the proxy manager with a clear name, type SOCKS5 or HTTP, host, matching port, username, password.
Attach it to a profile; set time zone and geolocation from IP, en-US first, WebRTC masked.
Keep the fingerprint on the operating system you are really using.
Run the check, then launch and verify on an IP page and a WebRTC test.

Cloud profiles take their clock from the profile settings, so the Eastern time zone still matters there.
Stop the profile, rotate, confirm the new address, start again; never rotate mid-session.

FoxyProxy

Browser extension

The quick way to put a normal Firefox or Chrome through a line without a separate browser, with per-site switching if you want it.

Install FoxyProxy and add a new proxy: type SOCKS5, host and SOCKS5 port, username and password.
Enable proxy DNS in the SOCKS5 options so lookups leave through the carrier.
Select the proxy for all URLs, or add patterns for only the sites you want through New York.
Open an IP check page and confirm the carrier and city.

Your normal browser keeps its own fingerprint and cookies; this is for convenience, not isolation.
WebRTC in a normal browser may leak your real address; disable it in about:config or with a flag if that matters.

Proxifier

System-wide proxy client

Forces every application on Windows or macOS through the line, including software with no proxy setting of its own.

Add a proxy server: SOCKS5, host, SOCKS5 port, enable authentication, enter username and password.
Set name resolution to resolve hostnames through the proxy.
Create a rule for the applications you want through the line, or set the default rule to the proxy.
Check with Proxifier's built-in test, then with an IP page in any browser.

Exclude your own remote-control or VPN software from the rules so you do not lock yourself out.
For a whole-machine setup the VLESS tunnel is simpler and encrypted; Proxifier shines for per-app rules.

Shadowrocket

iOS client

An iPhone client that imports our VLESS link or a SOCKS5 login and routes the whole phone through the New York line.

Open the VLESS section of your line in the dashboard and show the QR code.
In Shadowrocket tap add, scan the QR code, and select the new server.
Set the global routing mode so every app goes through the tunnel.
Connect, then check an IP page and a maps app to confirm New York.

Set the iPhone's region to United States and time zone to Eastern first.
The tunnel survives a rotation; reload the IP page after rotating to see the new address.

Android system proxy

Android

Android's own Wi-Fi proxy setting, or an Xray client for a full tunnel. Use this on your own phone or on one of our Android phone plans.

For a quick test: long-press the Wi-Fi network, modify, advanced, proxy manual, enter host and HTTP port; this covers browsers but not every app.
For everything: install an Xray-based client, scan the VLESS QR code from the dashboard, and connect.
Set the phone's region to United States and time zone to Eastern.
Verify with an IP page and with an app that reads location.

The Wi-Fi proxy setting does not take a username and password on most builds; the Xray client is the reliable route.
Our Android phone plans are already on the carrier; nothing to configure, the phone is the line.

Python requests

Scripting

The standard way to script through a line in Python, with the proxy in a dictionary and the same credentials for HTTP and SOCKS5.

Install requests and the socks extra so SOCKS5 is available.
Build a proxies dictionary with socks5h://username:password@host:port for both http and https keys; the h makes DNS go through the proxy.
Pass proxies to a Session so every request on that session uses the line.
Fetch an IP check URL first and assert the carrier and city before doing real work.

Set a realistic User-Agent and a pace a person would keep; the line looks like a phone, your script should not look like a flood.
Call the rotation link from the same script and poll our API until the address changes before continuing.

curl

Command line

The fastest way to prove a line works and to see exactly what a site gets, in one command from any terminal.

Run curl with the proxy flag pointing at socks5h://host:port and the user flag with username:password.
Fetch an IP check service and read the carrier and city in the response.
Repeat with the HTTP port and the http:// scheme to confirm both work.
Add the verbose flag if something fails; the error tells you whether it is auth, port or connectivity.

Put the credentials in a netrc file or an environment variable rather than your shell history.
curl through the line is also how we debug on our side, so send us the output if you open a ticket.

Playwright

Browser automation

Headless or headed Chromium, Firefox and WebKit through the line, with proxy credentials passed at launch and a New York time zone set on the context.

Launch the browser with a proxy object: server set to the HTTP port, username and password filled in.
Create a context with timezoneId America/New_York and locale en-US.
Open an IP page in the context and assert carrier and city before running the job.
Keep one browser per line; do not share a line across parallel workers that are supposed to be unrelated.

Playwright's proxy works at the browser level, so all contexts in that browser share the line.
Set a viewport and user agent that agree with each other; a desktop viewport claiming to be a phone is an odd signal.

Node fetch

Scripting

Node's built-in fetch with a proxy agent, for small monitors and checks that run on a schedule through the line.

Install a SOCKS or HTTPS proxy agent package for Node.
Create an agent with socks5h://username:password@host:port, or the HTTP port with an HTTPS proxy agent.
Pass the agent in the fetch options, or set it as the global dispatcher if the whole process should use the line.
Fetch an IP check URL at startup and log the carrier and city with each run.

Schedule checks at a human cadence; a monitor that polls every few seconds is what sites are built to notice.
Rotate between runs by calling the rotation link, not between requests.

Windows proxy settings

Operating system

Windows' own proxy setting for a whole user session, when you want Edge, Office and most apps through the line without extra software.

Open Settings, Network and Internet, Proxy, and turn on manual proxy setup.
Enter the host and the HTTP port; save.
Open a browser; when prompted, enter the line's username and password.
Check an IP page and confirm the carrier and New York.

Windows' setting is HTTP only and some apps ignore it; for everything, use the VLESS tunnel or Proxifier.
Set the Windows time zone to Eastern so the system clock agrees with the address.

Postman

API testing

Test your own APIs and third-party endpoints from a New York carrier address, which is what your mobile users actually come from.

Open Settings, Proxy, and add a custom proxy with the host and HTTP port.
Enable proxy authentication and enter the username and password.
Send a request to an IP check endpoint and confirm the response shows the carrier and city.
Run your collection; responses now reflect what a New York mobile client gets.

Useful for checking geo-dependent API responses, rate behaviour and carrier-specific routing.
Switch the plan to another carrier from the dashboard and rerun the collection to compare.

Settings that are the same everywhere

Whatever the tool, four things decide whether a session looks like a New Yorker on a phone. The address, which the line provides. The time zone, which must be Eastern. The locale, which should be en-US. And DNS, which should leave through the line rather than your home provider, which SOCKS5 with remote resolution or the VLESS tunnel both handle. Get those four right and the rest of the fingerprint only has to be internally consistent.

Address: the line
Time zone: America/New_York
Locale: en-US
DNS: through the proxy or tunnel

HTTP, SOCKS5 or VLESS

Every line has all three. HTTP is the simplest and works in anything with a proxy field. SOCKS5 carries any TCP traffic plus UDP and can resolve names remotely, which is why we prefer it for browsers and scripts. VLESS is an encrypted tunnel for a whole device, best for phones and for machines where several apps need the line. They share the same address and the same rotations.

Rotation from any tool

The rotation link is a URL. Open it from a browser, call it from curl, from a Python script, from a Node monitor or from a scheduled task, and the modem re-registers with the carrier for a fresh address. There is no waiting between rotations. Our API also reports the current address, so a script can poll until the change lands before it continues. For account work, rotate between sessions, not during them.

A tool we have not listed

If it speaks HTTP or SOCKS5 it will work, and if it can import a vless:// link it will work with the tunnel. Message @NewYorkProxiesBot or [email protected] with the tool's name and we will tell you the settings, or test it ourselves on a line and add it here.

Integration questions

Do I need to tell a tool which borough the line is in?

No. Nothing about the borough is visible to a tool or a site; the address reads as New York City. The borough only matters to us for signal and stock.

Can one line serve a browser and a script at once?

Yes, with the same credentials. They share the address, so a rotation from one changes the other.

Which tool is best for a phone?

An Xray-based client with the VLESS link, on Android or iOS, so every app goes through the line. Or skip the setup and rent one of our Android phone plans, which is already on the carrier.