Skip to main content
FlameProxies authenticates proxy requests with a username and password. Every package and sub-user has its own credentials.

​
Where to find your credentials

To find your credentials:
  1. Log in to the dashboard.
  2. Open the package you want to use. Its username and password are shown there, and are included in every line the proxy generator creates.
  3. If you’re connecting as a sub-user, use that sub-user’s own username and password.
You can also read a package’s credentials with the Customer API: GET /api/customer/packages/:id returns its username and password.

​
Username/password authentication

You send your credentials with every request as part of the proxy line. The format is:
The username field is your package username followed by your parameters (product, location, session, pool, and modes). The password field is your package password. Here’s a basic example that routes through a US residential IP:
You should get a response like this:
The package parameter is required. If you leave out country, the gateway can pick an IP from any country.

​
Adding more parameters

You can chain parameters in the username field, using hyphens as delimiters. Here are some examples: Target a specific country and city:
Use the premium pool with a 20-minute sticky session:
Use fast mode for lower latency:
The full list of parameters is in the Residential proxies reference.

​
Supported protocols

Residential and premium residential proxies use the same gateway. Pick the port for your protocol: For example, the same request over SOCKS5:
Static residential (ISP) proxies use a dedicated host for each IP instead of the shared gateway. See Static residential proxies.

​
Output formats

Tools expect proxy details in different layouts. The dashboard and the Customer API can give you any of these four: Here’s the same proxy in each layout:
standard
secondary
http_url
socks5_url
When you use SOCKS5 with URL output, use the socks5_url layout and port 1080.

​
Keeping your credentials safe

Anyone with your username and password can spend your bandwidth.
  • Load credentials from environment variables or a secrets manager, not from source code.
  • Never commit credentials to git or ship them in client-side code.
  • Give each integration, team, or customer its own sub-user with only the bandwidth it needs. If one set of credentials leaks, only that sub-user’s bandwidth is exposed.
Proxy credentials ≠ API key. Your package username and password authenticate proxy traffic through proxy.flameproxies.com. The Customer API uses a separate API key (fp_live_…). See API authentication.

​
Errors

If the gateway rejects your credentials over HTTP, it responds with 407 Proxy Authentication Required. The most common causes are:
  • A typo in the username or password. Copy both exactly from the dashboard.
  • A missing or misspelled package parameter. It must be package-standard or package-premium.
  • Parameters in the password field. Parameters always go in the username, after your package username.
See Connection debugging for a full checklist.

​
Next steps

Residential proxies

Full parameter reference for residential proxies.

Premium residential proxies

Full reference for premium residential proxies.

Proxy generator

Generate proxy lines from the dashboard without memorizing the format.

Connection debugging

What to do if you get a 407 or a timeout.