Get all runs by agent
List runs for a specific workflow.
Supports filtering by status, search_key, and error_code. All filters are combined with AND logic.
search_key
Case-insensitive substring search across: workflow run ID, parameter key, parameter description, run parameter value, and extra HTTP headers. Soft-deleted parameter definitions are excluded.
error_code
Exact-match filter on the error_code field inside each task’s errors JSON array. A run matches if any of its tasks contains an error with a matching error_code.
include_child_runs
Child runs — runs this workflow started from inside another workflow run — are excluded by default, so the history shows only top-level runs. Pass include_child_runs=true to list them as well; every run carries a parent_workflow_run_id that is null for top-level runs.
Headers
Skyvern API key for authentication. API key can be found at https://app.skyvern.com/settings.
Path Parameters
Query Parameters
Page number for pagination.
x >= 1Number of runs to return per page.
x >= 1Filter by one or more run statuses.
created, queued, running, failed, terminated, canceled, timed_out, completed, paused Case-insensitive substring search across: workflow run ID, parameter key, parameter description, run parameter value, and extra HTTP headers. A run is returned if any of these fields match. Soft-deleted parameter definitions are excluded from key/description matching.
500"login_url"
Exact-match filter on the error_code field inside each task's errors JSON array. A run matches if any of its tasks contains an error with a matching error_code. Error codes are user-defined strings set during workflow execution.
500"INVALID_CREDENTIALS"
Only include runs created at or after this UTC timestamp (ISO 8601).
Only include runs created strictly before this UTC timestamp (ISO 8601).
Filter by run tags. Each term is a label (production), a group (env:*), or a group:label (env:prod). Repeat the param or comma-separate (?tags=env:prod,env:staging). AND across distinct terms, OR within a group's labels (?tags=customer:acme,env:prod,env:staging -> customer=acme AND env in (prod, staging)). A label term matches the value across any/no group. Matches current tag values only.
20"env:prod"
Include child workflow runs — runs started from inside another workflow run. Excluded by default so the history shows only top-level runs.
Response
Successful Response
created, queued, running, failed, terminated, canceled, timed_out, completed, paused Which layer of the seed-precedence chain seeded a run's browser (provenance).
Resolved once at run setup, before any browser creation, for all run types (C-semantics).
- override: explicit request browser_profile_id (one-run-only pick via API)
- picked: the workflow's explicit profile pick (workflows.browser_profile_id) — "always start here"
- own_memory: the workflow's own auto-profile (no pick + persist_browser_session)
- credential: the run's selected credential's profile (rotation-aware; also the empty-own boot)
- fresh: no seed profile
- degraded_fresh: a resolved profile failed to load; ran fresh
override, picked, own_memory, credential, fresh, degraded_fresh One-based number of the current workflow run attempt
Whether another attempt is scheduled for this workflow run
Timestamp when the next workflow run attempt is scheduled
Attempts recorded for this workflow run
RESIDENTIAL, US-CA, US-NY, US-TX, US-FL, US-WA, RESIDENTIAL_ES, RESIDENTIAL_IE, RESIDENTIAL_GB, RESIDENTIAL_IN, RESIDENTIAL_JP, RESIDENTIAL_FR, RESIDENTIAL_DE, RESIDENTIAL_NZ, RESIDENTIAL_ZA, RESIDENTIAL_AR, RESIDENTIAL_AU, RESIDENTIAL_BR, RESIDENTIAL_TR, RESIDENTIAL_CA, RESIDENTIAL_MX, RESIDENTIAL_IT, RESIDENTIAL_NL, RESIDENTIAL_PH, RESIDENTIAL_KR, RESIDENTIAL_SA, RESIDENTIAL_ISP, NONE How a workflow run was initiated.
- manual: User clicked "Run" in the UI
- mcp: First-party MCP client request
- api: Direct API call to the run endpoint
- scheduled: Triggered by a cron schedule
- webhook: Triggered by an external system via the webhook endpoint
- job_recipe_extract: Launched by a job recipe extract request
- job_recipe_apply: Launched by a job recipe apply request
manual, mcp, api, scheduled, webhook, job_recipe_extract, job_recipe_apply 
