Skip to content

Exchange an Automation Secret

Exchange an automation secret for an access token.

Best for Automation developer and Workspace manager Updated April 3, 2026
API In this interface
4 steps Steps
1 examples Examples
Use this path when

Exchange the automation secret for an access token before calling scoped workspace APIs.

What you'll finish here
  • Use the right credential in the right place.
  • Mint a short-lived access token safely.
  • Know when to repeat the exchange.

Where this happens

LabelValueNotes
EndpointPOST /api/v1/automation-auth/exchangeAutomation secret exchange endpoint.

Same Task, Other Interfaces

Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.

Keep this boundary clear

  • The long-lived automation secret is not the token you should keep reusing on normal resource endpoints.

Do the work

  1. 1. Send the long-lived automation secret as the bearer token in the `Authorization` header.
  2. 2. Read the returned short-lived access token and expiry timestamp.
  3. 3. Use the short-lived access token on resource endpoints such as `/api/v1/workspaces/{workspaceId}/tasks` or `/api/v1/workspaces/{workspaceId}/projects`.
  4. 4. Repeat the exchange when the short-lived token expires.

Exchange an automation secret

bash
curl -X POST http://localhost:5173/api/v1/automation-auth/exchange   -H 'authorization: Bearer blg_auto_secret_here'

Keep Going in Automation and Agents

Stay in the same interface and move to the next closest task in this topic when needed.

Nearby Guides

These guides stay close to the current workflow so you can keep moving without restarting discovery.