Integration Antidetect browser

Kameleo Proxy Integration

Kameleo masks fingerprints across desktop and mobile profiles and exposes a local API for automation, but the exit IP is yours to supply. This guide covers where Kameleo keeps its proxy channel, how the proxy test tool validates a connection, and how to run each profile on a ProxyOmega residential IP.

Get started All integrations

200+countries
1.5M+residential IPs
60 hrmax sticky session

Kameleo

What is Kameleo?

Kameleo is an antidetect browser aimed at professionals and automation-heavy teams. It spoofs browser and device fingerprints, can emulate mobile profiles alongside desktop ones, and is known for a well-documented local REST API and SDKs that make it a favourite for Selenium, Playwright and Puppeteer automation at scale.

Each profile isolates cookies, storage and a complete fingerprint, and Kameleo includes a built-in proxy manager plus a proxy test tool. As with every antidetect browser, Kameleo manages the identity but not the IP address, so a proxy provider supplies the network layer.

Kameleo

Why Kameleo needs residential proxies

Kameleo can present each profile as a unique desktop or mobile device, but it cannot alter the IP address the traffic exits from. Several profiles sharing one IP can be correlated regardless of fingerprint quality, so the IP must come from a proxy, and residential IPs are what real users have.

Because datacenter ranges are broadly flagged, residential IPs from genuine consumer lines are the safe choice for account work and scraping alike. The reliable pattern is one clean residential IP per Kameleo profile, held stable across a session.

Isolate every profile

Give each profile its own sticky IP with a unique -session- tag. Sharing an IP between profiles undoes Kameleo's isolation and links the accounts.

Test before launch

Kameleo's proxy test tool checks the connection without starting the browser, so you can confirm the ProxyOmega credentials and geo are correct before you commit a profile to a task.

API-friendly

Kameleo's local API lets you create profiles with a proxy defined in code, ideal for spinning up many profiles programmatically, each with its own session-pinned residential IP.

Kameleo

How to set up ProxyOmega in Kameleo

In Kameleo you set the proxy channel when creating a profile, choosing HTTP or SOCKS5 (Kameleo also lists SSH, which you do not need here). Enter the server, port, username and password, then run the proxy test tool. The same settings can be defined through Kameleo's API for automated profile creation.

Targeting rides on the username with dash-separated parameters, and the password is your ProxyOmega account API key.

Click 'New profile' and select a base fingerprint (desktop or mobile).
Open the proxy/connection settings and set the channel to 'HTTP' or 'SOCKS5'. Both run on the same ProxyOmega port.
In the 'Server' (host) field enter residential.proxyomega.com and set 'Port' to 10000 (any assigned port in 10000-10199).
Set the 'Username' with targeting, for example youruser-country-de-session-k09-ttl-1440.
Set the 'Password' to your ProxyOmega account API key from the dashboard.
Run Kameleo's proxy test tool and confirm a successful connection and the expected country before launching.
Save the profile. To reuse the configuration, store it in Kameleo's built-in proxy manager and change only the -session- id per profile.
For automation, pass the same host, port, username and API key as the proxy object when creating a profile via the Kameleo API.

Kameleo

Which ProxyOmega plan to pick

Kameleo works with any ProxyOmega plan; pick by workload. Automation and high-volume profiles suit Budget Unlimited, while precise targeting or a fixed identity calls for a premium tier.

Workload	Plan	Why
Automated or high-volume profiles	Budget Unlimited	Flat port-based pricing with a unique sticky IP per profile via -session- ids.
Precise geo (country, state, city, ASN)	Platinum	Pay-per-GB Tier-1 residential with full geo and ASN targeting on port 20228.
Mobile-profile emulation with real carrier IPs	Mobile	Genuine 4G/5G carrier IPs with country and session on port 20229.
A permanent fixed US IP	Static ISP	Dedicated Dallas IP on isp.proxyomega.com that never rotates.
Speed-critical automation	Premium Unlimited	Dedicated 200Mbps-1Gbps tier on premium.proxyomega.com:8000.

Kameleo

Troubleshooting

A failed Kameleo proxy test almost always comes down to the API key, an unsupported username parameter, or a whitelist. Check them in order.

407 or proxy test failed

Use your ProxyOmega API key as the password, not your dashboard login. Then confirm every dash-parameter on the username is supported by the plan; an unsupported parameter rejects the entire username and returns 407.

Test passes but the profile will not browse

This usually means IP whitelisting is enabled. When any IP is whitelisted, only whitelisted IPs work and credentials are ignored. Whitelist the machine running Kameleo or clear the whitelist to use credential auth.

Wrong country in the test result

Fix the two-letter -country- code on the username and re-run the proxy test so Kameleo re-reads the exit IP's location.

SOCKS5 channel fails

Use the same host and port as HTTP and set the channel to SOCKS5. ProxyOmega serves SOCKS5 on the same port, so there is no separate SOCKS5 port to look for.

FAQ

Frequently asked questions

Can I set a ProxyOmega proxy through the Kameleo API?

Yes. When creating a profile via Kameleo's local API, define the proxy with type http or socks5 and a server object holding the host, port, username (with targeting) and the API key as the secret.

What is the Kameleo password for ProxyOmega?

Your ProxyOmega account API key from the dashboard, not your dashboard login password. The wrong password makes the proxy test fail.

Does Kameleo's proxy test work with ProxyOmega?

Yes. The proxy test tool checks the connection without launching the browser. A successful result confirms the host, port, username and API key are correct before you use the profile.

How do I keep a Kameleo profile on one IP?

Add -session- with a unique id and -ttl- in minutes to the username. The same session id holds the same sticky IP for up to 60 hours.

Does Kameleo support SOCKS5 with ProxyOmega?

Yes. Set the channel to SOCKS5 and use the same residential.proxyomega.com host and port you use for HTTP. All ProxyOmega ports serve HTTP, HTTPS and SOCKS5.

Can Kameleo emulate a mobile profile on a residential IP?

Yes. Choose a mobile base fingerprint and attach a ProxyOmega residential IP, or use the Mobile plan on port 20229 for real 4G/5G carrier IPs when a profile needs to look like a mobile connection.

Run every Kameleo profile, desktop or mobile, on a residential IP Start routing today.

Test before launch, automate with the API, scale across 200+ countries.

Get started