> ## Documentation Index > Fetch the complete documentation index at: https://developers.flameproxies.com/llms.txt > Use this file to discover all available pages before exploring further. # Authentication > How to authenticate with FlameProxies using your package username and password. Includes the proxy line format, where to find credentials, supported protocols, and output formats. 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](https://flameproxies.com/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](/dashboard/proxy-generator) creates. 3. If you're connecting as a [sub-user](/dashboard/sub-users), 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`](/api/packages/get) returns its `username` and `password`. ## Username/password authentication You send your credentials with every request as part of the proxy line. The format is: ```text theme={null} proxy.flameproxies.com:8989:-package-standard[-parameters]: ``` 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: ```bash theme={null} curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us:PASSWORD" https://ipinfo.io/json ``` You should get a response like this: ```json theme={null} { "ip": "203.0.113.45", "city": "Los Angeles", "country": "US", "timezone": "America/Los_Angeles" } ``` 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:** ```text theme={null} proxy.flameproxies.com:8989:-package-standard-country-us-city-newyorkcity: ``` **Use the premium pool with a 20-minute sticky session:** ```text theme={null} proxy.flameproxies.com:8989:-package-premium-country-gb-session-c3d4-time-20: ``` **Use fast mode for lower latency:** ```text theme={null} proxy.flameproxies.com:8989:-package-standard-country-de-mode-fast: ``` The full list of parameters is in the [Residential proxies](/proxies/residential#full-parameter-reference) reference. ### Supported protocols Residential and premium residential proxies use the same gateway. Pick the port for your protocol: | Protocol | Host | Port | | - | - | - | | HTTP (including HTTPS sites via CONNECT) | `proxy.flameproxies.com` | `8989` | | SOCKS5 | `proxy.flameproxies.com` | `1080` | For example, the same request over SOCKS5: ```bash theme={null} curl --socks5-hostname proxy.flameproxies.com:1080 --proxy-user "USERNAME-package-standard-country-us:PASSWORD" https://ipinfo.io/json ``` Static residential (ISP) proxies use a dedicated host for each IP instead of the shared gateway. See [Static residential proxies](/proxies/static-residential). ## Output formats Tools expect proxy details in different layouts. The dashboard and the Customer API can give you any of these four: | Format | Layout | | - | - | | `standard` | `host:port:username:password` | | `secondary` | `username:password@host:port` | | `http_url` | `http://username:password@host:port` | | `socks5_url` | `socks5://username:password@host:port` | Here's the same proxy in each layout: ```text standard theme={null} proxy.flameproxies.com:8989:-package-standard-country-us-city-newyorkcity-session-a1b2-time-30: ``` ```text secondary theme={null} -package-standard-country-us-city-newyorkcity-session-a1b2-time-30:@proxy.flameproxies.com:8989 ``` ```text http_url theme={null} http://-package-standard-country-us-city-newyorkcity-session-a1b2-time-30:@proxy.flameproxies.com:8989 ``` ```text socks5_url theme={null} socks5://-package-standard-country-us-city-newyorkcity-session-a1b2-time-30:@proxy.flameproxies.com:1080 ``` 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](/dashboard/sub-users) with only the bandwidth it needs. If one set of credentials leaks, only that sub-user's bandwidth is exposed. ```python theme={null} import os username = os.environ["FLAME_USERNAME"] password = os.environ["FLAME_PASSWORD"] proxy_url = f"http://{username}-package-standard-country-us:{password}@proxy.flameproxies.com:8989" ``` **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](/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](/troubleshooting/connection-debugging) for a full checklist. ## Next steps Full parameter reference for residential proxies. Full reference for premium residential proxies. Generate proxy lines from the dashboard without memorizing the format. What to do if you get a 407 or a timeout.