Export workflow run data
Workflow Run Export API
Workflow Run Export API
Export workflow run and node execution data as JSON for analysis and debugging.
GET
Export workflow run data
Use the Workflow Run Export API to export workflow run and node execution data as JSON. Each row gives you run metadata, node status, and detailed execution data when you have access to the node.
You receive one row for each node execution. A run without node executions returns one row with
For a dedicated deployment, replace
Rows are ordered from oldest to newest by run creation time and then node execution creation time. The endpoint does not paginate. Use a narrower date range to reduce the response size.
Malformed query parameters return
Before you start
Before you start, make sure you have:- Workspace API key: Create a workspace API key with the
WORKFLOW_APIscope under Settings > Workspace > Products > API. Personal API keys only support the Completion APIs. See Personal API keys. - Workflow access: The API key must belong to a workflow owner or editor. Workspace administrators can also access workflows without a workflow share. A workflow shared with the User role does not grant access to this endpoint, including for workspace administrators.
Base URL
- Langdock Cloud
- Dedicated Deployment
Endpoint
null node fields.
Authentication
Send your API key as a Bearer token:cURL
https://api.langdock.com with your deployment base URL.
Parameters
Include
Z or an explicit UTC offset in full timestamps. A timestamp without a timezone is interpreted in the server’s local timezone. Both date values are required. The API does not apply a default date range. You receive every node execution for a matching run, even if the node execution falls outside the date range.
Response
You receive adata array with flattened workflow run and node execution rows:
Success
Response fields
The
input and output fields are null for execution data older than 30 days. All five payload fields are null when the endpoint cannot establish access to the node’s data. This can happen when your workflow access does not include an action or agent node used by the execution. The API sets data_redacted to true in that case.
For payload values larger than 16,000 bytes, the API returns a truncation marker. The marker contains an _truncated object with originalBytes, maxBytes, and message fields.
The response does not include the identity of the person or group that triggered a run.
Limits and retention
- Each request can export up to 10,000 workflow runs.
- Input and output data is retained for 30 days.
- Payload data in one response is limited to 8,000,000 bytes.
400 Bad Request with the WORKFLOW_RUN_EXPORT_LIMIT_EXCEEDED code. If the payload data exceeds 8,000,000 bytes, it returns 400 Bad Request with the WORKFLOW_RUN_EXPORT_TOO_LARGE code. Use a smaller date range to resolve either error.
Rate limits
The endpoint allows 500 requests per minute for each workspace and API key. Requests above the limit return429 Too Many Requests.
Error handling
Error
{"message":"Invalid request","errors":[...]} without a code field. An invalid date or a to value earlier than from returns code: "BAD_REQUEST".
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, see API Key Best Practices.
Authorizations
API key as Bearer token. Format "Bearer YOUR_API_KEY"
Path Parameters
ID of the workflow to export.
Query Parameters
Start of the export range. Use an ISO 8601 date or timestamp. A date-only value starts at 00:00:00.000 UTC.
End of the export range. Use an ISO 8601 date or timestamp. A date-only value ends at 23:59:59.999 UTC.
Response
Workflow run export
Flattened workflow run and node execution rows.