Proxy setup, start to finish

Your first job is to receive the access token and store it somewhere reliable. Every ProxyTow account is built around a token that begins with pw_, and that string unlocks the dashboard while also acting as the proxy password.

When the sign up screen shows the token, copy the string or grab the .txt download, then tick 'I saved it' to finish creating the account. The server stores just a hashed form of it, so the copy you keep at that moment is the one that counts.

A password manager or an encrypted note makes the token easy to reach from several devices. Up to three accounts can be opened from one IP address, which suits a small team that prefers separate balances.

• Copy the string or keep the .txt download.
• Tick the confirmation box to create the account.
• Keep the token in at least two safe places.

Funding happens through a USDT transfer on TRC20, and it takes only a handful of steps once you know the order. Pick an amount card in the Top up area or type your own figure, and the dashboard returns a receiving address plus a precise amount carrying six decimal places.

In your wallet or exchange, enter that figure down to the last digit. The six decimal tail is how the system matches the transfer to your request. A request remains valid for 60 minutes, and if the window closes before you send, simply create a fresh one.

Choose TRC20 (Tron) as the network every time. Deposits range from $20 up to $10,000, and visitors connecting from the 72 countries the World Bank ranks in its low or lower middle income groups can start from $10. Larger deposits earn a bonus on the $100 +20%, $200 +25%, $300 +30%, $500 +35%, $1,000 +40%, $3,000 +45%, $5,000 +50% scale, so sending $300 leaves $390 in your balance.

• Choose a card or enter a custom amount.
• Copy the address and the six decimal amount.
• Send via TRC20 before the 60 minute window ends.
• Funds appear after the transfer clears.

Location and session are both controlled by the username string. The simplest form puts a country code after user-country, and narrowing to a city adds a city part written in lower case with underscores between words.

Adding a session part to the string pins one IP for up to 90 minutes while that label keeps being used. Leave the part out and each request gets a new IP.

Mobile traffic needs type-mobile in the string. If typing these by hand feels slow, open Build access details, pick a location and session, then copy the output as HTTP, SOCKS5, a colon separated line or a curl command.

• user-country-us: a fresh US IP for each request.
• user-country-us-city-new_york: narrowed to New York.
• user-country-jp-session-shop1: a Japanese IP held through the session.
• user-type-mobile-country-gb: a mobile IP in the United Kingdom.

For opening web pages or collecting data, HTTP is the easy starting point. Nearly every library and browser accepts an HTTP proxy out of the box, so the settings form stays short.

SOCKS5 fits when traffic beyond web pages has to pass through, or when you want to route an entire application. Both protocols share the gateway at gate.proxytow.com:7000, with identical login details.

When a tool shows separate fields, put the gateway in host and port, the string you built earlier in username, and your pw_ token in the password box. Tools that take a single line accept the string copied from Build access details as it stands.

• HTTP: suits scraping, browsers and common libraries.
• SOCKS5: suits app traffic and mixed protocols.
• One gateway and one login serve both.

Connecting from code comes down to handing one proxy URL to your HTTP client. Begin with a quick terminal test, curl -x http://gate.proxytow.com:7000 -U "user-country-de:pw_TOKEN" https://api.ipify.org?format=json, and confirm the reply shows a German location before moving on.

In Python requests, build a proxies dictionary with http and https keys and point both at the same URL holding the username, token and gateway. Attach it once to a Session object and every call made through that session travels via the proxy.

In Node.js, pass the same URL to a popular proxy agent package and plug that agent into fetch or your HTTP client options. Keeping the token in an environment variable instead of the source file keeps your repository tidy when you push changes.

If a job hops between countries, write a small helper that only swaps the username. Feed it a country code and a session label, and switching location becomes a one line change.

Inside a browser, a proxy extension or an antidetect browser profile is the most comfortable route. Either one lets you give an IP to a single window or profile while the rest of the system keeps its normal connection.

In a proxy extension, create a new profile and fill in the protocol (HTTP or SOCKS5), the gateway, the username string and the token. Antidetect browsers include a proxy field for every profile, and pasting one host:port:user:pass line usually splits into the right boxes by itself.

If you manage several accounts, assign every profile a distinct session label, say shop1 for one and shop2 for another, so each keeps a separate IP for the length of the session. Setting the profile's clock and language to suit the chosen country makes it look even more natural.

• Extensions: one set of access details per profile.
• Antidetect browsers: a different session label per profile.
• After connecting, confirm the country on an IP lookup page.

Scraping frameworks plug into the same proxy URL, and the real decision is between rotating and sticky sessions. Jobs that sweep many pages, such as search results or product listings, do best when every request leaves from a new IP.

Flows that must look like one visitor, such as logins, carts or multi step forms, should carry a session label so the IP stays put for up to 90 minutes. Creating a new label for every job gives each flow its own clean address.

Scrapy accepts the proxy in a request's meta field or through a middleware that applies it everywhere. Playwright and Puppeteer take the server address at launch and authenticate with the username and token. Selenium sets the proxy in browser options, and when an auth prompt appears, an extension or helper tool supplies the credentials.

• Rotating: wide sweeps such as listings and search pages.
• Sticky: connected steps such as login and checkout.
• Give every job its own session label.

Plans with a fixed term, meaning ISP, dedicated or shared datacenter, IPv6 and unlimited residential, are bought from the dashboard's Buy products page, and each one's access details are shown inside My orders. The price leaves your balance the moment you confirm, and the order is marked Preparing.

Once activation completes, the status switches to Active and the order reveals access details for that specific product. ISP orders take 1 to 500 IPs and dedicated datacenter 1 to 1,000, while shared datacenter and IPv6 move in blocks of ten. Terms of one, three, six or twelve months are available.

Unlimited residential runs for one, seven or thirty days and behaves like rotating residential, so the same session label rules apply. Should an order be cancelled or refunded, the money goes back to your balance and can be spent on another product immediately.

• Choose product, quantity and term under Buy products.
• Watch for the Preparing status in My orders.
• Copy the access details once it shows Active.

When a connection behaves unexpectedly, correcting the credentials or a single character in the username usually sorts it out right away. A 407 response is a cue to check that the full pw_ token sits in the password box with no stray spaces at either end.

If the IP lands in another country, confirm the country part uses two lower case letters and that city names use underscores. Frequent timeouts call for widening the target from city to country or switching to a fresh session label to try another IP.

If a typo crept in while copying the token, swapping in a fresh string from Build access details is the quickest fix. Check that your balance has room as well, and accounts with a credited first top up can describe the issue through customer support.

• 407: check the full token and trailing spaces.
• Wrong country: check the country code and city spelling.
• Timeouts: widen the target or start a new session.
• Typos: copy again from Build access details.