Multilogin X · API
The Multilogin X API, mapped for operators
If you buy Multilogin for ads, MMO, or automation, the Postman collection is the real product manual. This page translates that collection into “what do I open when X breaks?” — not a pirate copy of their documenter.
Canonical docs (always win in a conflict):
API needs Pro or higher on Multilogin’s side. Free five-profile accounts are for UI trials — see pricing.
Folders you’ll actually touch
Profile Access Management
Sign in (password as MD5 hash per Multilogin’s guide), refresh token, automation tokens. Bearer tokens expire fast (help text cites ~30 minutes for the session token). When every call returns 401, start here — not by rewriting Playwright. Our walkthrough: API auth · troubleshooting: token errors.
Launcher
Start / stop browser profiles. For automation you pass an automation type (playwright, puppeteer, or selenium) so the response includes a local port. Official Playwright samples use the local launcher host pattern launcher.mlx.yt:45001 with folder_id and profile_id in the path. The Multilogin agent/app must be running. Attach CDP from that port — Playwright guide · CDP errors.
Profile Management
Create, search, update, remove profiles. This is how agencies keep “one ad account ≈ one profile” from turning into a spreadsheet fire. Folders double as geo/offer partitions for media buyers.
Proxy
Attach and manage proxies on profiles. Geo mismatch (proxy exit vs profile timezone/language) causes more “fingerprint” panic than WebGL ever will. Ops notes: proxy + Multilogin · formatter tool · proxy errors.
Browser Profile Data / Pre-made Cookies
Cookie and session hygiene for warmup — not a promise of safe accounts. Read cookies guide and warmup checklist.
Everything else (Script Runner, bookmarks, object storage, import/export)
Power-user surfaces. We don’t re-host Multilogin’s full schema. Open the Postman documenter folder when you need them; our job is routing you there without sales fog.
Typical automation loop (ads / MMO tech)
1. Sign in / refresh token (PAM)
2. Ensure proxy + folder/profile IDs are known
3. Launcher: start profile with automation_type=playwright
4. Connect Playwright/Puppeteer to 127.0.0.1:{port}
5. Do the job (slowly, per account)
6. Stop profile; refresh token before the next waveWho this is for
- Ads multi-account · Facebook / Meta ads desks · Google ads
- Affiliate / arbitrage operators
- Engineers wiring CDP farms — kits in our monorepo + public Playwright/Puppeteer starters
Get SAAS50 / MIN50 Postman setup Open official API