GET/v1/runtasks

Get Run Tasks

Retrieve a list of all tasks executed within a specific run

This endpoint retrieves a paginated list of all tasks executed within a specific run, including their individual status, results, and parameters.

Headers

KeyValueRequired
AuthorizationToken YOUR_API_KEYYes

Query Parameters

run
Type:
string
Required:
Yes
Description:
The run hash ID to get tasks for
page
Type:
integer
Required:
No
Description:
Page number for pagination. Default: 1
limit
Type:
integer
Required:
No
Description:
Results per page. Default: 50, Max: 100

Response Field Explanations

total_results
integer
Total number of run tasks
Example: 1
data
array
Array of run task objects
Example: [...]
data[].id
string
Unique run task identifier
Example: 1262f6f99dac7dffb05a513fff0ded77
data[].object
string
Always "runtask"
Example: runtask
data[].task
string
Original task identifier
Example: d30334cd8d21ab16048c5e2e7136a9f1
data[].run
string
Parent run identifier
Example: 300e9c5c127d421c90f431478d9a2cfb
data[].status
string
Task execution status (completed, aborted, error, etc.)
Example: aborted
data[].params
object
Task parameters
Example: {url: https://...}
data[].started_at
string
When task execution started
Example: 2025-02-10T14:30:58Z
data[].ended_at
string
When task execution ended
Example: 2025-02-10T14:31:10Z
data[].total_results
integer
Total results expected from this task
Example: 138
data[].last_result
integer
Number of results actually collected
Example: 6
data[].total_pages
integer
Total pages processed
Example: 1
data[].done_reason
string
Reason for task completion
Example: run_aborted
Pro Tip

Pro Tip

Use this endpoint to debug which specific tasks failed or were incomplete in a run.
Note

Note

The done_reason field on individual tasks can differ from the overall run's done_reason.
Pro Tip

Pro Tip

Compare total_results vs last_result to see if a task collected all expected data.