Integrations

Whatever sends the traffic, it talks to us the same way: standard HTTP proxy authentication on one host and port. Pick what you run below for the exact fields, a copy-paste snippet and how to tell it worked.

The fields every integration asks for

Whatever the tool calls them, it wants the same four values. The login and password come from your dashboard; the endpoint is the same for every product we sell.

Proxy type

HTTP

Host

gate.avocadoproxies.com

Port

8080

Username / Password

From your dashboard

One combined value is gate.avocadoproxies.com:8080. Some tools want host and port typed separately, others want them as one string. Either is the same connection.
Targeting keys go on the username, never in a separate field: USERNAME-cc-de for a German exit. Full grammar on the targeting page.
Every example below uses USERNAME and PASSWORD as placeholders. Read the real values from an environment variable or your secrets manager, and never commit them.

Sticky or rotating is also set by the username. Leave it plain and every connection may exit from a different address; add -sid-<id> and everything sharing that id holds one address, for up to as long as you say with -ttl-<minutes>. Each integration below shows where that goes for that tool; see Sticky sessions for the full rules.