Error desk

Token & auth errors

If every Launcher call is 401, stop debugging CDP ports. You have a PAM / token problem.

Most common mistakes

• Sending a raw password instead of the MD5 hex Multilogin’s Postman help expects.
• Keeping a Bearer token past ~30 minutes without refresh / automation token.
• Calling cloud APIs from a machine that never signed in successfully in Postman first.
• Expecting Free-plan API — Free has no API; need Pro+ — pricing.

Fix path

1. Reproduce sign-in in Postman — Postman guide.
2. Follow API auth; store token in env, never git.
3. Then start profile — API map.

What a good sign-in looks like

POST https://api.multilogin.com/user/signin
Content-Type: application/json

{ "email": "you@example.com", "password": "<md5 hex of password>" }

→ data.token  (help text: ~30 minutes)

Hash the password the way Multilogin’s official samples do — do not invent base64. Confirm with Postman before rewriting Node.

After you have a token

• Pass Authorization: Bearer {token} to Launcher https://launcher.mlx.yt:45001/... start calls.
• On 401 mid-job: re-signin or refresh; don’t rotate proxy settings as a “fix.”
• CDP timeouts that appear after ~30 minutes are often dead tokens — CDP desk.

Ads desks

Auth failures during peak ad ops look like “Playwright died.” Check token age first, then proxy. Lanes: Facebook · Google.

Get Multilogin deal CDP errors