Per-request flag overrides
Append flags to your proxy username to change routing and identity per request — without changing your dashboard defaults. This page lists the flags you can set and the exact rule for which value wins.
How overrides work
Your dashboard holds your default settings. For a single request you can override them by appending flags to your proxy username. The brain merges your per-request flags with your defaults and resolves exactly one value per flag. Spoof inputs such as tls and ua only emit when spoofing is enabled for your subscription.
Per-request flags
Two delimiter styles
Pick one style and use it consistently — you cannot mix the two in a single username.
Dash style
Append flags after your username as -key-value pairs.
myuser-country-de-session-abc123Semicolon style
Append flags after your username as ;key=value pairs.
myuser;country=de;session=abc123Which value wins
Highest precedence first. Lists replace your default for that flag — they do not concatenate.
- 1.
-none (explicit removal)
Highest precedence: explicitly removes a flag so nothing else can set it.
- 2.
Per-request basic-auth value
A value you append to the username for this request overrides your dashboard default.
- 3.
Dashboard default
Your saved default applies when you do not set the flag for this request.
- 4.
Omitted
If no source sets the flag, it is left off entirely.
Worked examples
Per-request beats your dashboard default
Dashboard default country=us, request adds country-de
Resolves to: de
-none removes a flag entirely
Dashboard default country=us, request adds country-none
Resolves to: removed (no country sent)
Absent everywhere is omitted
No dashboard default and nothing on the request
Resolves to: omitted (flag left off)