🧩 Fingerprint BrowserEnvironment Overview
To handle fingerprinting browser and automation detection on modern websites, the platform automatically provisions and hosts an isolated browser fingerprint environment during script execution. This environment is used for operations that require a real browser context, such as JavaScript rendering, page interaction, login sessions, and authenticated access. The fingerprint environment is fully maintained by the platform.Developers do not need to deploy, purchase, or manage fingerprint browser instances to access a stable and reliable browser runtime. This mechanism effectively reduces failures and account-linking risks caused by repeated device characteristics or duplicated browser fingerprints.
📌 Fingerprint Environment Configuration
- Browser Type: Chromium (platform-hosted remote instance)
- Connection Method:
WebSocket - Access Endpoint: Internal platform browser service
- Authentication
- Environment Variable:
PROXY_AUTH - Format:
username:password
- Environment Variable:
- Usage: Read
PROXY_AUTHin your script and construct the WebSocket URL to connect - Pricing: Built-in, no extra cost, no additional setup required
🐍 Python Example
🧱 Go Example
🟢 Node.js Example
⚠️ Notes & Best Practices
- ❗ Never hardcode proxy credentials
- ❗ **Always use the platform-injected **
PROXY_AUTHenvironment variable - ✅ The fingerprint browser is automatically provisioned and rotated by the platform
- ✅ No manual browser setup or proxy configuration is required