Executions API
API endpoints for tracking and managing tool executions in the Kubiya platform
Executions API
The Executions API allows you to track and manage tool executions in the Kubiya platform. Every time a tool is executed by an AI Teammate, the execution details are recorded and can be queried using this API.
This playground makes API calls to Kubiya API through a secure server-side proxy. Your requests never expose your API token directly to the browser.
List Executions
Retrieve a list of tool executions based on various filters.
Headers
Name | Required | Description |
---|---|---|
Authorization | Yes | UserKey YOUR_API_KEY |
Query Parameters
Name | Type | Required | Description |
---|---|---|---|
tool_id | string | No | Filter by tool ID |
teammate_id | string | No | Filter by teammate ID |
status | string | No | Filter by status (success , failure , pending ) |
limit | number | No | Maximum number of results (default: 20) |
offset | number | No | Pagination offset |
from_date | string | No | Filter executions after this date (ISO format) |
to_date | string | No | Filter executions before this date (ISO format) |
Response
Get Execution Details
Retrieve detailed information about a specific execution.
Path Parameters
Name | Type | Required | Description |
---|---|---|---|
execution_id | string | Yes | ID of the execution |
Headers
Name | Required | Description |
---|---|---|
Authorization | Yes | UserKey YOUR_API_KEY |
Response
Get Tool Executions
Retrieve a list of executions for a specific tool.
Path Parameters
Name | Type | Required | Description |
---|---|---|---|
tool_id | string | Yes | ID of the tool |
Headers
Name | Required | Description |
---|---|---|
Authorization | Yes | UserKey YOUR_API_KEY |
Query Parameters
Name | Type | Required | Description |
---|---|---|---|
status | string | No | Filter by status (success , failure , pending ) |
limit | number | No | Maximum number of results (default: 20) |
offset | number | No | Pagination offset |
from_date | string | No | Filter executions after this date (ISO format) |
to_date | string | No | Filter executions before this date (ISO format) |
Response
Get Teammate Executions
Retrieve a list of executions for a specific teammate.
Path Parameters
Name | Type | Required | Description |
---|---|---|---|
teammate_id | string | Yes | ID of the teammate |
Headers
Name | Required | Description |
---|---|---|
Authorization | Yes | UserKey YOUR_API_KEY |
Query Parameters
Name | Type | Required | Description |
---|---|---|---|
tool_id | string | No | Filter by tool ID |
status | string | No | Filter by status (success , failure , pending ) |
limit | number | No | Maximum number of results (default: 20) |
offset | number | No | Pagination offset |
from_date | string | No | Filter executions after this date (ISO format) |
to_date | string | No | Filter executions before this date (ISO format) |
Response
Example Usage
List Recent Executions
Get Execution Details
Get Tool Executions
Get Teammate Executions
The Executions API is useful for monitoring tool usage, troubleshooting issues, and gathering analytics about how your AI Teammates are performing various tasks.
Common Errors
HTTP Status | Description |
---|---|
400 | Bad Request - Invalid parameters or filters |
401 | Unauthorized - API key is missing or invalid |
403 | Forbidden - The API key doesn't have permission to access these executions |
404 | Not Found - The specified execution, tool, or teammate was not found |
500 | Internal Server Error - An unexpected error occurred on the server |
Next Steps
After analyzing executions, you can:
- Use insights to improve your tools
- Adjust teammate configurations based on execution patterns
- Set up webhooks to automatically respond to execution events