Skip to main content
GET
List workflow runs
Returns paginated runs and node executions for a workflow the API key user can edit. Use this path when you need filters such as test versus production, or a cursor. Flattened export with a required date range is a different contract on Workflow Run Export.

Base URL

Dedicated deploymentsReplace api.langdock.com with <your-deployment-url>/api/public in all requests.

Required scopes

This endpoint requires the WORKFLOW_API scope (Workflow Read API) and editor access.

Parameters

Unavailable action or agent data is redacted. Execution payloads follow the workflow API payload limit.

Example

Response format

Success response (200 OK)

Error handling

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.

Authorizations

Authorization
string
header
required

API key as Bearer token. Format "Bearer YOUR_API_KEY"

Query Parameters

workflowId
string<uuid>
required

UUID of the workflow.

limit
integer
default:50

Number of runs to return.

Required range: 1 <= x <= 100
cursor
string<uuid>

Run UUID from nextCursor in the previous response.

runId
string<uuid>

Filter to a single run UUID.

runMode
enum<string>
Available options:
test,
production
status
enum<string>
Available options:
PENDING,
IN_PROGRESS,
AWAITING_INPUT,
COMPLETED,
FAILED,
CANCELLED
from
string

Start of the run creation range. ISO 8601 timestamp or YYYY-MM-DD. Must be sent together with to.

to
string

End of the run creation range. Must be equal to or later than from.

version
string

Workflow version used for the run. Version 0 is the draft used for test runs.

Response

Workflow runs returned successfully