Endpoints & authentication

Gateways

Region	Endpoint
Europe	eu.tpp.io:1080
United States	us.tpp.io:1080

Connect to the region closest to your infrastructure. The gateway only decides where your connection enters the network; the exit IP is chosen by your targeting, and the full pool is reachable from every region.

Protocols

Every gateway speaks three protocols on the same port, auto-detected:

• HTTP CONNECT - what curl -x http://... and most HTTP clients use. HTTPS traffic tunnels through this.
• Plain HTTP forwarding - absolute-form requests (GET http://host/path) for plain-HTTP targets.
• SOCKS5 - with username/password authentication. Works for any TCP protocol.

Target hosts can be domains, IPv4 or IPv6 addresses. Domains are resolved from the exit’s network vantage, so geo-fenced content resolves the way it would for that household - prefer socks5h:// over socks5:// in clients that distinguish them, so your machine doesn’t resolve the name locally.

Authentication

Credentials go in the proxy username and password:

curl -x http://USER:PASS@eu.tpp.io:1080 https://example.com

The username is your proxy user, optionally followed by targeting options (USER-cc-de-session-abc). The password is always just your proxy password.

Proxy usernames are 3-64 characters of letters, digits, _ or . - no hyphens, since the hyphen separates targeting options. Credential changes made in the dashboard or API reach the gateways within a few seconds.

A failed authentication (HTTP 407, or a SOCKS5 auth failure) means one of:

• wrong username or password
• a malformed or unknown targeting option - options are validated, never silently ignored
• your bandwidth balance is exhausted
• your account is disabled

Metering

Usage is metered in bytes, both directions, against your prepaid balance. When the balance runs out, authentication starts failing - connections are never cut mid-transfer. Check your balance on the dashboard or via GET /v1/me.