Node.js

Node’s built-in fetch borrows undici’s proxy support, so pointing it at us is one call. For axios, https-proxy-agent does the same job.

Point your client at the gateway

Both approaches take the same proxy URL: gate.avocadoproxies.com on port 8080, login and password as Basic auth, targeting keys on the username.

javascript

import { ProxyAgent, setGlobalDispatcher } from "undici";

setGlobalDispatcher(new ProxyAgent("http://USERNAME-cc-de:PASSWORD@gate.avocadoproxies.com:8080"));

// Node's built-in fetch now goes through the gateway — no other import needed.
const response = await fetch("https://example.com");
console.log(response.status);

proxy: false matters in the axios example: without it, axios’ own proxy handling and the agent’s fight over the same connection, and the request can leave unproxied without an error.

Rotating per request

Leave the username plain, with no -sid-, and every call above is free to exit from a different address. The dispatcher and agent are reused; only the exit changes.

Add -sid-a1b2c3 to the username and every request carrying it holds one exit address; add -ttl-30 to bound how long, in minutes. See Sticky sessions for lifetimes and patterns.

Test it. Run either snippet. A 200 means the tunnel and your login both worked. Open Dashboard → Usage → Live and watch the request land within a few seconds.
For anything else, see the troubleshooting page.