Overview
Multilogin provides isolated browser profiles with unique fingerprints and native automation APIs — useful when standard headless Chrome or single-profile setups trigger blocks at scale. This guide covers a production-oriented launch flow for teams using Playwright, Puppeteer, or Selenium.
Need ready-made snippets? Use @Multilogin_Scripts_Bot on Telegram for launch checklists and diagnostic scripts.
Prerequisites
- Active Multilogin account with API access
- Profile template with consistent fingerprint preset
- Residential or datacenter proxy aligned to target geo
- Automation runtime: Node.js (Playwright) or Python (Selenium)
Setup steps
- Validate API credentials — Test token against workspace list endpoint. Log HTTP status and response body on failure.
- Align proxy with profile geo — Mismatch between IP country, timezone, and browser locale is a top detection vector. Set all three consistently.
- Launch profile via API — Use explicit timeouts (30–60s). Implement exponential backoff for transient 5xx errors.
- Attach automation driver — Read CDP WebSocket URL from launch response. Connect Playwright via
connectOverCDPor Selenium with debugger address. - Run smoke test — Visit a fingerprint audit page twice in the same profile. Compare Canvas hash stability between sessions.
- Scale gradually — Increase concurrent profiles in batches of 5–10. Monitor RAM, API quotas, and proxy rotation health.
Common errors
| Symptom | Likely cause | Fix |
|---|---|---|
| Profile launch timeout | Proxy dead or API overload | Validate proxy; retry with backoff |
| CDP attach fails | Profile not fully started | Poll status endpoint before connect |
| Immediate captcha | Geo/locale mismatch | Realign proxy + timezone preset |
| Session flagged after N runs | Canvas drift or shared cookies | Fresh profile; audit fingerprint |
Resources
Promo codes for evaluation: SAAS50 (50% off SaaS), MIN50 (minutes plan).
Disclosure: MLX-MMO is affiliated with Multilogin.