Use Badass proxies in minutes
Everything below uses Badass-branded gateways and your own purchased plan credentials. The high-volume residential plan supports country targeting plus rotating or sticky sessions up to 120 minutes.
HTTP / HTTPS
Connect through proxy.badass.fo:7443.
SOCKS5
Connect through proxy.badass.fo:7444.
Customer API
Generate proxy credentials programmatically with revocable API keys.
Quick start
Use credentials exactly as generated in your dashboard.
curl -x "http://USERNAME:PASSWORD@proxy.badass.fo:7443" https://api.ipify.orgcurl --socks5-hostname "proxy.badass.fo:7444" --proxy-user "USERNAME:PASSWORD" https://api.ipify.orgRotating and sticky sessions
Session behavior is encoded in the username generated for the plan.
Use the base username (optionally with country targeting). The residential exit can rotate between requests.
USERNAME-country-usAdd a session identifier and duration. The high-volume residential plan accepts durations from 1–120 minutes.
USERNAME-country-us-session-abc123-time-30Targeting
The high-volume residential plan supports country targeting; city/state targeting is not exposed on that plan.
No country suffix. Uses the global pool.
Generator adds -country-us.
Badass sends a Europe country-code pool.
Select any supported ISO-2 country from the generator.
Useful formats
Choose the format expected by your browser, scraper, automation framework or proxy manager.
Customer API
Create a key under Dashboard → Developer API. Keys are shown in full only once when created.
/api/v1/plansList your proxy plans/api/v1/plans/:planId/usageSync/read one plan's usage/api/v1/countriesList supported country codes/api/v1/proxies/generateGenerate proxy credentialscurl -X POST "https://backend.badass.fo/api/v1/proxies/generate" \
-H "Authorization: Bearer bad_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"planId":"PLAN_ID","protocol":"http","countries":["US"],"sessionMode":"sticky","stickyMinutes":30,"count":10}'Authentication: Authorization: Bearer bad_live_.... API keys can read plans and generate credentials, but intentionally cannot spend wallet balance. Add GB from the authenticated dashboard.
Troubleshooting
The fast checks that solve most connection problems.
Generate a fresh line and make sure the username, password, hostname and port stay in the format expected by your application.
Keep the same session ID and duration while the session is active. A different session ID intentionally creates a different sticky session.
Try both HTTP and SOCKS5, then check the dashboard/network status. Badass routes Lite traffic through its branded relay.
Usage syncs periodically from the network and can lag live traffic slightly. Manual refresh requests a fresh reading.