Skip to content

Developers

API

Your systems can start automations, read their results and send events into work.studio. Pick the way in that fits what you’re building.

Way in Use it to Credential
REST API Run automations and read runs from any language API key in X-API-Key
Incoming webhooks Let another service start an automation when something happens Webhook signing secret, optionally an API key
MCP Let Claude Code, VS Code or another MCP client work with your organization Your work.studio sign-in
TypeScript SDK (@workstudio-inc/sdk) Embed the catalog in your product, or build an app your own users sign in to Embed key and session tokens, or your app’s sign-in
Python SDK (workstudio) Call work.studio from Python API key
App Kit (npx workstudio deploy) Host your App’s front-end at https://<address>.workstudio.run Organization API key

Every API path starts with https://api.work.studio/api/v1/workflow/.

  • TypeScript and JavaScript: npm i @workstudio-inc/sdk (0.11.x). The main entry point is the headless embed client. @workstudio-inc/sdk/app is the App SDK for apps whose own users sign in. The package has no client for running automations with an API key; use the REST API for that.
  • Python: pip install workstudio (0.1.x). It reads your key from WORKSTUDIO_API_KEY. workflows.list() and workflows.get() need an organization key (svx_tk_): a customer key can’t read automation definitions and gets 403. With only Run Automation, they return a summary of each automation (its id, name and inputs); the full definition needs View Automation.