Enable the Automation API and get your token

Turn on the Automation API in the desktop app's Automation panel, then copy the Bearer token and local port.

The Automation API is off by default. Before any script can drive your profiles, you turn it on in the desktop app and copy two things: your Bearer token and the port the local server listens on.

This is a Team plan feature, and everything stays on your own machine — the server binds to 127.0.0.1 and is protected by a token that only you hold.

Turn it on

  1. 1Open the desktop app and go to the Automation panel.
  2. 2Enable the Automation API. The app starts a local HTTP server on 127.0.0.1 (default port 36912).
  3. 3Copy the Bearer token shown in the panel.
  4. 4Note the port — you'll use it in your script's base URL, e.g. http://127.0.0.1:36912.

Test that it's live

Send a quick health check with your token to confirm the server is up:

curl -H "Authorization: Bearer YOUR_TOKEN" \
  http://127.0.0.1:36912/sw/health
# -> { "ok": true, "product": "...", "version": "..." }

You can also pass the token as a query parameter instead of a header: append ?token=YOUR_TOKEN to any endpoint.

Regenerate the token

You can regenerate the token from the Automation panel at any time. This is useful if the token may have leaked, or after sharing your machine.

Heads up

Regenerating the token invalidates the old one. Any script or session still using the previous token will stop working until you update it with the new value.

Still need a hand?

Email our team and a real person will get back to you, usually within a few hours.

[email protected]
Try in the cloud →Start free trial