Get Detailed Tasks for a Specific Run
Runs - Executions & calls
Get Detailed Tasks for a Specific Run
Retrieve all tasks with full execution details for a specific run
GET
Get Detailed Tasks for a Specific Run
Documentation Index
Fetch the complete documentation index at: https://docs.unpod.dev/llms.txt
Use this file to discover all available pages before exploring further.
Get Detailed Tasks for a Specific Run
Fetch all tasks for a specific run, including complete input, output, call transcript, costs, analysis, artifacts, and provider metadata. This endpoint is used when you need deep inspection of how a run executed each task.Prerequisites: Make sure you have your API Token ready. See Authentication for details.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| space_token | string | Yes | Public token of the space |
| run_id | string | Yes | The run ID whose tasks to retrieve |
You can get the
space_token from the Get All Spaces API. The run_id can be obtained from the Get All Runs API response.Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | API Key format: Token <token> |
| Content-Type | string | Yes | application/json |
Response Fields
| Field | Type | Description |
|---|---|---|
| count | integer | Total number of tasks |
| status_code | integer | HTTP status code |
| message | string | Response message |
| data | array | Array of task objects |
Task Object Fields
| Field | Type | Description |
|---|---|---|
| _id | string | Internal task document ID |
| thread_id | string | Thread identifier |
| user_info | object | User details (email, full_name) |
| task_id | string | Unique task identifier |
| run_id | string | Parent run identifier |
| task | object | Task definition with objective |
| input | object | Input data for the task |
| output | object | Task output including call details |
| assignee | string | Agent handle assigned to the task |
| status | string | Task status: pending, completed, failed |
| execution_type | string | Type of execution: call, email, etc. |
| created | string | Task creation timestamp |
| modified | string | Last modified timestamp |
Output Object Fields
| Field | Type | Description |
|---|---|---|
| call_id | string | Unique call identifier |
| start_time | string | Call start timestamp |
| end_time | string | Call end timestamp |
| duration | number | Call duration in seconds |
| recording_url | string | URL to call recording |
| transcript | array | Array of conversation messages |
| post_call_data | object | Post-call analysis data |
| call_type | string | Direction: outbound, inbound |
| call_status | string | Status of the call |
Common Error Codes
| Status Code | Description |
|---|---|
| 200 | Success - Data fetched successfully |
| 206 | Partial Content - Business logic error occurred |
| 400 | Bad Request - Invalid parameters provided |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Access denied to the resource |
| 404 | Not Found - Space or Run not found |
| 500 | Internal Server Error - Server-side error |
Code Examples
Best Practices
- Run ID: Always retrieve the
run_idfrom the Get All Runs endpoint first - Transcript Review: Use the
transcriptarray in output for conversation quality analysis - Recording Access: Store
recording_urlfor compliance, QA, and playback - Post-call Data: Check
post_call_data.summaryfor AI-generated call summaries and outcomes - Error Handling: Always handle potential errors and edge cases
- Security: Keep API tokens secure and rotate them regularly
Authorizations
Format: Token
Headers
Organization domain handle
Example:
"unpod.tv"
Path Parameters
Example:
"8KZAMRAHSXXXXXXMAYNASMJC"
Example:
"Recac64fe03e911f1878d43cd8a99e069"
Response
List of tasks for the run