How to set up LatamProxies proxies (2026)

How is the proxy username built?

All targeting goes into the username, so you never need a different host or port per country. The full format is USERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}. Every part after USERNAME is optional.

• USERNAME alone: a rotating IP from any supported country.
• USERNAME-country-mx: a rotating IP in Mexico.
• USERNAME-country-ar-city-buenos_aires: a rotating IP in Buenos Aires.
• USERNAME-country-br-session-abc123-ttl-30: the same Brazilian IP for up to 30 minutes.

Country codes are two-letter ISO codes in lower case. City names are lower case with _ instead of spaces and no accents: sao_paulo, not São Paulo. Do not add other parameters: the gateway does not read ASN, ZIP or carrier parameters in the username.

How do I test the proxy with cURL?

cURL is the fastest way to check that your credentials and targeting work. The request below goes through the HTTP gateway and prints the exit IP. Replace USERNAME and PASSWORD with the values from your dashboard.

curl -x http://gw.latamproxies.com:7777 \
  -U "USERNAME-country-br:PASSWORD" \
  https://api.ipify.org?format=json

curl --socks5-hostname gw.latamproxies.com:7778 \
  -U "USERNAME-country-mx-city-mexico_city-session-abc123-ttl-30:PASSWORD" \
  https://api.ipify.org?format=json

How do I use the proxy with Python requests?

With requests, set the same proxy URL for both http and https. HTTPS targets are tunnelled through the HTTP gateway with CONNECT, so the URL scheme of the proxy stays http://. For SOCKS5, install requests[socks] and use socks5h:// so DNS is resolved through the proxy, in the target country.

import requests

USER = "USERNAME-country-co"
PASS = "PASSWORD"
proxy = f"http://{USER}:{PASS}@gw.latamproxies.com:7777"

proxies = {"http": proxy, "https": proxy}
r = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=30)
print(r.json())

# pip install "requests[socks]"
import requests

USER = "USERNAME-country-br-city-sao_paulo-session-job42-ttl-30"
PASS = "PASSWORD"
proxy = f"socks5h://{USER}:{PASS}@gw.latamproxies.com:7778"

with requests.Session() as s:
    s.proxies = {"http": proxy, "https": proxy}
    for _ in range(3):
        print(s.get("https://api.ipify.org?format=json", timeout=30).json())  # same IP 3 times

How do I use the proxy with Node.js?

In Node.js 18 or later, the built-in fetch does not read proxy settings, so use undici's ProxyAgent and pass it as the dispatcher. With axios, use https-proxy-agent and set proxy: false so axios does not apply its own proxy logic.

// npm install undici
import { fetch, ProxyAgent } from 'undici';

const user = 'USERNAME-country-ar';
const pass = 'PASSWORD';
const dispatcher = new ProxyAgent({
  uri: 'http://gw.latamproxies.com:7777',
  token: 'Basic ' + Buffer.from(`${user}:${pass}`).toString('base64'),
});

const res = await fetch('https://api.ipify.org?format=json', { dispatcher });
console.log(await res.json());

// npm install axios https-proxy-agent
import axios from 'axios';
import { HttpsProxyAgent } from 'https-proxy-agent';

const user = encodeURIComponent('USERNAME-country-cl');
const pass = encodeURIComponent('PASSWORD');
const agent = new HttpsProxyAgent(`http://${user}:${pass}@gw.latamproxies.com:7777`);

const { data } = await axios.get('https://api.ipify.org?format=json', {
  httpsAgent: agent,
  proxy: false,
  timeout: 30000,
});
console.log(data);

How do I use the proxy with Playwright?

Playwright accepts the proxy server, username and password at launch. Use a sticky session for browser work: a page loads many resources, and one IP per page keeps the session consistent. Change the session id to get a new IP for the next browser context.

// npm install playwright
import { chromium } from 'playwright';

const browser = await chromium.launch({
  proxy: {
    server: 'http://gw.latamproxies.com:7777',
    username: 'USERNAME-country-pe-city-lima-session-pw1-ttl-30',
    password: 'PASSWORD',
  },
});
const page = await browser.newPage();
await page.goto('https://api.ipify.org?format=json');
console.log(await page.textContent('body'));
await browser.close();

# pip install playwright && playwright install chromium
from playwright.sync_api import sync_playwright

with sync_playwright() as p:
    browser = p.chromium.launch(proxy={
        "server": "http://gw.latamproxies.com:7777",
        "username": "USERNAME-country-br-session-pw2-ttl-30",
        "password": "PASSWORD",
    })
    page = browser.new_page()
    page.goto("https://api.ipify.org?format=json")
    print(page.text_content("body"))
    browser.close()

How do I use the proxy with Puppeteer?

Chrome does not accept credentials inside --proxy-server, so Puppeteer passes the server as a launch argument and the username and password with page.authenticate().

// npm install puppeteer
import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({
  args: ['--proxy-server=http://gw.latamproxies.com:7777'],
});
const page = await browser.newPage();
await page.authenticate({
  username: 'USERNAME-country-mx-city-mexico_city-session-pp1-ttl-30',
  password: 'PASSWORD',
});
await page.goto('https://api.ipify.org?format=json');
console.log(await page.evaluate(() => document.body.innerText));
await browser.close();

Should I use rotating or sticky sessions?

Use rotating IPs for independent requests and sticky sessions for multi-step flows. New IP on every request, or sticky sessions up to 30 minutes.

• Rotating (no session): best for crawling many product pages, such as Mercado Libre price monitoring, or for checking search results from many places.
• Sticky (-session-ID-ttl-30): best for browser automation, pagination that depends on cookies, checkout-flow testing on your own store and ad verification journeys.

For 4G/5G dedicated ports, rotation works differently: you change the IP through an API link. See the mobile proxy rotation guide.

What do common errors mean?

Most problems come from the username string or from the target site:

• 407 Proxy Authentication Required: the username or password is wrong. Check for spaces, and URL-encode special characters in the password.
• Connection refused or timeout on connect: check the host and port. HTTP uses 7777, SOCKS5 uses 7778.
• Wrong country: check the country code (br, not bra) and the city spelling (sao_paulo).
• 403 or CAPTCHA from the target: slow down, rotate more often, or use a sticky session with a real browser.
• Target refused by the gateway: banks, government portals, payment portals and SMTP are blocked by our Acceptable Use Policy.

If the problem continues, email [email protected] with your username string (without the password), the target and the error.