---
title: "Proxy Integrations: Python, Node.js & Puppeteer | Proxonym"
description: "Step-by-step proxy setup guides for cURL, Python Requests, Scrapy, Node.js, Puppeteer, Playwright, Selenium, Go, PHP, Java, AdsPower and Multilogin."
url: https://proxonym.com/integrations
updated: 2026-10-01T21:01:06+00:00
---

# Proxy integrations for the tools you already use.

Proxonym speaks standard HTTP, HTTPS and SOCKS5, so any client that accepts a proxy works. These guides take you from install to a verified, geo-targeted request in minutes.

The same four values everywhere

- **Host**: `gw.proxonym.com`
- **HTTP / HTTPS port**: `8000`
- **SOCKS5 port**: `1080`
- **Username**: `USERNAME-country-us`

Targeting and sessions go in the username, so every tool gets country, city and sticky IPs without plugins.

## Setup guides 12

- [cURL (Command line)](https://proxonym.com/integrations/curl): cURL is the quickest way to test a proxy from a terminal. These commands send requests through the Proxonym gateway, pin a sticky IP, target a location and decode gateway errors.
- [Python Requests (Python)](https://proxonym.com/integrations/python-requests): Requests only needs a proxies dictionary to send traffic through Proxonym. This guide covers authentication, location targeting, rotating and sticky IPs, SOCKS5 and retries for gateway errors.
- [Scrapy (Python)](https://proxonym.com/integrations/scrapy): Scrapy reads the proxy for each request from request.meta. A short downloader middleware sends every request through Proxonym, and individual requests can override it with their own session or location.
- [Selenium (Python)](https://proxonym.com/integrations/selenium): Selenium cannot type into a proxy login prompt, but WebDriver BiDi can answer it for you. This guide uses Python and Firefox to authenticate with Proxonym, hold sticky IPs, target locations and recover from errors.
- [Node.js (JavaScript)](https://proxonym.com/integrations/nodejs): Node.js sends fetch requests through a proxy with an undici ProxyAgent. This guide authenticates against the Proxonym gateway, rotates or pins IPs, targets locations, adds SOCKS5 and retries errors.
- [Playwright (JavaScript)](https://proxonym.com/integrations/playwright): Playwright accepts proxy settings, username and password included, at launch or for each browser context. This guide covers authentication, sticky IPs per context, location matching and resilient navigation.
- [Puppeteer (JavaScript)](https://proxonym.com/integrations/puppeteer): Puppeteer points Chrome at a proxy with a launch flag and answers the gateway login with page.authenticate(). This guide adds sticky sessions, one IP per browser context, location matching and leaner page loads.
- [Go](https://proxonym.com/integrations/go): Go needs no third-party packages for proxies: net/http handles authenticated HTTP and SOCKS5 gateways. This guide covers rotation, sticky sessions, location targeting and reading gateway status codes.
- [PHP](https://proxonym.com/integrations/php): PHP reaches the Proxonym gateway through the cURL extension or Guzzle, which uses cURL underneath. This guide covers authentication, location targeting, rotating and sticky IPs, SOCKS5 and retries.
- [Java](https://proxonym.com/integrations/java): The HttpClient built into Java 11 and later supports authenticated proxies once one JDK default is changed. This guide covers that setting, sticky sessions, location targeting and retries for gateway errors.
- [AdsPower (Anti-detect browser)](https://proxonym.com/integrations/adspower): AdsPower stores a proxy with every browser profile. This guide connects profiles to the Proxonym gateway, gives each one a stable IP through a session ID, and aligns the fingerprint with the exit location.
- [Multilogin (Anti-detect browser)](https://proxonym.com/integrations/multilogin): Multilogin saves a proxy inside every browser profile. These steps add the Proxonym gateway as a custom proxy, keep a stable IP per profile with a session ID, and verify the connection before launch.

## Using another tool? It works too.

No guide for your tool? If it has a proxy field or reads the standard proxy environment variables, it works with Proxonym.

- **Command-line tools and SDKs**: Most read `HTTP_PROXY` and `HTTPS_PROXY` automatically.
- **Desktop apps and browsers**: Enter the host, port and credentials in the proxy settings.
- **Any HTTP library**: Pass the proxy URL; nine languages are covered in the docs.

**Environment variables**

```bash
# Most tools also read these environment variables
export HTTP_PROXY="http://USERNAME-country-us:PASSWORD@gw.proxonym.com:8000"
export HTTPS_PROXY="$HTTP_PROXY"

curl https://api.ipify.org   # prints a US residential IP
```
