How to Set Up Multilogin Automation with Postman

Why Postman first

Postman is ideal to:

• Prove auth headers and base URLs
• Document start/stop profile payloads for the team
• Share a collection without distributing ad-hoc scripts

Once calls are stable, port the same contract into Puppeteer, Selenium, or script runner.

Setup steps

1. Create an environment with baseUrl, token, workspaceId.
2. Never commit the environment file with live secrets.
3. Add an auth request (or set a Bearer token) per your MLX API version.
4. Create requests for: list profiles, start profile (automation flags as needed), stop profile.
5. Use Tests tab to assert status === 200 and to save profile_id into environment variables.
6. Run the folder as a collection runner with a tiny concurrency first.

Example environment keys

baseUrl      = http://127.0.0.1:35000
token        = ***
workspaceId  = ********-****-****-****-************
profileId    = (set by tests)

Header pattern

Authorization: Bearer {{token}}
Content-Type: application/json

Collection hygiene

From Postman to production

When low-code is no longer enough:

1. Copy working payloads into code.
2. Add trace_id, retries, and quarantine.
3. Enforce the token runbook.

Need seats or Minutes? Partner codes on the Multilogin deals page.