Get your credentials and learn how to authenticate with Floppydata
Floppydata uses two authentication methods depending on which product you’re using.Authentication methods
| Product | Authentication | Format |
|---|---|---|
| Proxies | Username + Password | Passed in proxy connection string |
| Web Unlocker | API Key | Passed in X-Api-Key header |
| Client API | API Key | Passed in X-Api-Key header |
Getting your credentials
Log in to dashboard
Go to app.floppydata.com and log in
Using proxy credentials
Connection format
Example
Available ports
| Port | Protocol | Use case |
|---|---|---|
10080 | HTTP | Default, works with most tools |
10443 | HTTPS | Secure HTTP connection |
10800 | SOCKS5 | Advanced use, automation tools |
Adding Smart Parameters
Smart Parameters control proxy behavior. They’re added to the username:Learn more about Smart Parameters
See all available parameters and how to use them.
For Web Unlocker
Pass your API key in theX-Api-Key header:
For Client API endpoints
Same format for all Client API requests:Testing your connection
Test proxy connection
Simple test with cURL:If you see a different IP than your own → Proxy is working!
Test API key
If you see your balance → API Key is working!
Quick setup examples
- Python
- Node.js
1. Install dependencies2. Create .env file3. Use in your code
Managing API keys
Creating new keys
Rotating keys
Why rotate?
- Security best practice
- Compromised credentials
- Team member changes
- Regular maintenance
- Generate new API key
- Update your applications with new key
- Test that new key works
- Delete old key from dashboard
Deleting keys
- Go to Dashboard → Settings → API Keys
- Find the key to delete
- Click Delete icon
- Confirm deletion
Troubleshooting
407 Proxy Authentication Required
407 Proxy Authentication Required
Cause: Incorrect username or passwordSolutions:
- Double-check credentials in dashboard
- Ensure no extra spaces in username/password
- Try copying credentials again
- Check for special characters that need URL encoding
401 Unauthorized (API Key)
401 Unauthorized (API Key)
403 Forbidden
403 Forbidden
Cause: IP whitelisting enabled but your IP not addedSolutions:
- Check if IP whitelisting is enabled (Dashboard → Settings)
- Add your current IP to whitelist
- Get your current IP:
curl https://api.ipify.org
Connection Refused
Connection Refused
Cause: Wrong host or portSolutions:
- Verify host is
geo.g-w.info(not .com or other variations) - Check port: 10080 (HTTP), 10443 (HTTPS), or 10800 (SOCKS5)
- Check firewall settings