Base URL
API key scopes
Workflow access is split into three scopes. A key can hold any combination of them.
Create a workspace API key under Settings > Workspace > Products > API. A personal API key can include Workflow Read API, and Workflow Write API when your admin allows it. Workflow Deletion API cannot be granted on a personal key. See Personal API keys.
The API runs as the key’s configured user. Workspace keys run as a service account. Personal keys run as their owner.
Available endpoints
Paginated runs (
/workflows/v1/runs) return run objects with node executions, filters such as runMode, and a cursor. Flattened export (/workflows/{workflowId}/runs) returns date-bounded rows, is not paginated, and is capped at 10,000 runs.
Workflow object
Get, create, update, and publish return the same workflow object:nodes and edges are the draft graph (version 0). activeVersion is the published graph when one exists. Secret-like fields such as webhook secrets are redacted. Sending a redacted graph back in an update keeps the stored secrets.
Permissions
Created workflows stay private to the key until you pass
shareWith or someone shares them later. Workspace admins can share a workflow with an active workspace API key from Share. Use Search people, groups and API keys to find the key. Personal keys are not share targets because they already act as their owner.
Templates cannot be created, listed, or published through this API.
Rate limits
The Workflow API follows standard API rate limits. If you exceed the limit, you receive a429 response. Wait and retry with exponential backoff.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.