Authentication

ProxyOmega supports three ways to authenticate: IP whitelisting for credential-free access, username & password embedded in the proxy URL, and an API key for the REST API. All three are managed from your dashboard.

Overview

Every proxy connection you make must be authenticated so that traffic is attributed to your account. There are two ways to authenticate the proxy connection itself, by IP whitelist or by username & password, plus a separate API key used only for the REST API. The two proxy methods are mutually exclusive: pick one for your account, not both.

IP whitelist

Add your server's public IP in the dashboard and connect with no username or password. Best for machines with a static IP.

Username + password

Embed your credentials in the proxy URL: http://username:password@endpoint:port. Works from any IP.

API key

Authenticates the REST API: the api_key query parameter on proxy-list export, and the X-API-Key header on the Reseller API. Not used for the proxy connection itself.

Which method to use

Method	How you connect	Best for
IP whitelist	No credentials, just point at the endpoint and port	Servers with a fixed, static public IP
Username + password	`http://username:password@endpoint:port`	Dynamic IPs, laptops, rotating cloud workers, any source IP
API key	`api_key` query parameter (proxy-list export) or `X-API-Key` header (Reseller API)	Managing your account programmatically, not for proxy traffic

IP whitelist (credential-free)

Add your server's public IP under Whitelist in the dashboard, then connect to the proxy with no username or password. This is the simplest option when your source machine has a stable, static IP.

You can whitelist multiple IPs, so add every server or location you connect from.
Once an IP is whitelisted, connections from it are authenticated automatically, with no credentials required in the proxy URL.
Ideal for dedicated servers, VPS instances, and any host with a fixed public IP.

A non-empty whitelist locks the door. If you have any IPs on your whitelist, your account is IP-gated: connections from IPs that are not on it are refused, and username & password authentication stops working. Either whitelist every source IP you connect from, or remove all whitelist entries to switch back to username & password authentication.

Example: connect through Budget Unlimited from a whitelisted server, with no credentials in the URL.

curl -x http://residential.proxyomega.com:10000 https://api.ipify.org

Username + password

Embed your credentials directly in the proxy URL. Your username and password are shown in your dashboard. This method works from any IP, so it's the right choice when your source machine's IP changes or when you connect from many hosts.

curl -x http://username:[email protected]:10000 https://api.ipify.org

To target a specific country or configure sticky sessions, append targeting parameters to the username (the password stays unchanged). For example, to request a US IP:

curl -x http://username-country-us:[email protected]:10000 https://api.ipify.org

One method at a time. IP whitelisting and username & password are mutually exclusive. Adding any IP to your whitelist switches your account to IP-gated access and your username & password stop working; to authenticate with credentials, your whitelist must be empty. See Targeting for the full username parameter syntax and Sessions & rotation for sticky-IP control.

API key (REST API only)

The API key authenticates parts of the Public API, not the proxy connection. On the Public API it is passed as the api_key query parameter to the proxy-list export endpoint; account endpoints (whitelist, subscriptions, session info) use the bearer token from your dashboard session instead — see the API reference for exactly which scheme each endpoint takes. Regenerating your API key also rotates your proxy password — running clients need the new value within about a minute.

curl "https://proxyomega.com/api/v1/proxy-list?api_key=YOUR_API_KEY&type=platinum"

Don't confuse the two. Your API key never goes into a proxy URL, and your proxy username/password never goes into an API request. Proxy traffic uses the whitelist or username & password; the REST API uses the api_key parameter or a bearer token.

If you run a reseller account, the Reseller API uses a different scheme. It expects your API key in the X-API-Key header against https://dashboard.proxyomega.com/api/reseller/v1 and requires an approved, KYC-verified reseller account.

Finding and rotating your credentials

Everything is managed from your dashboard:

Proxy username & password. Shown alongside your subscription. Copy them straight into your proxy URL.
IP whitelist. Open the Whitelist section to add, view, or remove the IPs allowed to connect without credentials. You can add multiple IPs.
API key. View or rotate it in your account settings. Rotating the key invalidates the old one, so update any scripts that use it.
Proxy-list generator. Builds ready-to-paste connection strings (including targeting parameters) so you don't have to assemble them by hand.

✓

Next step. Ready to send your first request? Head to the Quickstart, or jump straight to your product's page: Budget Unlimited, Premium Unlimited, Residential / ISP, Mobile, IPv6, or Static ISP.

Last updated July 10, 2026