Get runs
Get runs for the organization with the variables you’ve added to your runs table.
Headers
Your API key for authentication. Use Bearer format.
"Bearer API_KEY"
The organization ID to use for the request. Required if your user is associated to more than one organization.
Query Parameters
The number of runs to return. Defaults to 1000.
x <= 5000
1000
The number of runs to skip. Defaults to 0.
500
The ID of the use case to filter runs by. Defaults to all runs in all use cases.
The status of the runs to filter by.
scheduled
, running
, completed
, canceled
, failed
The start date to filter runs by. Defaults to all runs.
"2024-01-01T00:00:00.000Z"
The end date to filter runs by. Defaults to all runs.
"2024-01-01T00:00:00.000Z"
The sort order of the runs by their timestamp (does not sort by completion date). Defaults to desc.
asc
, desc
"desc"
Filter runs by completion date, starting from this date. If not specified, includes runs completed at any time.
"2024-01-01T00:00:00.000Z"
Filter runs by completion date, ending at this date. If not specified, includes runs completed at any time.
"2024-01-01T00:00:00.000Z"
Filters based on a particular node output in the run. The syntax for this property is '{{node.id}}.property.to.filter.by': ['{{value}}']
. The simpliest way to get the key is to add the var to your runs table and to view the keys in the data
property of the /runs
response. If you need assistance with this, please reach out to your HappyRobot representative.
Response
200
A list of runs with the data for each column you've added to your runs table.