Retrieve run logs by AI contact or by voice call
curl --request GET \
--url https://api.vambe.me/api/public/run-logs \
--header 'x-api-key: <x-api-key>'const options = {method: 'GET', headers: {'x-api-key': '<x-api-key>'}};
fetch('https://api.vambe.me/api/public/run-logs', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.vambe.me/api/public/run-logs"
headers = {"x-api-key": "<x-api-key>"}
response = requests.get(url, headers=headers)
print(response.text)AI Run Logs
Retrieve run logs by AI contact or by voice call
Returns run logs as trees with their descendants. Scope the query with exactly one of ai_contact_id (ordered by start time descending) or voice_call_id (ordered ascending, so a call reads chronologically). Supports pagination over the root run logs.
GET
/
api
/
public
/
run-logs
Retrieve run logs by AI contact or by voice call
curl --request GET \
--url https://api.vambe.me/api/public/run-logs \
--header 'x-api-key: <x-api-key>'const options = {method: 'GET', headers: {'x-api-key': '<x-api-key>'}};
fetch('https://api.vambe.me/api/public/run-logs', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.vambe.me/api/public/run-logs"
headers = {"x-api-key": "<x-api-key>"}
response = requests.get(url, headers=headers)
print(response.text)Overview
Retrieve the AI run logs (assistant execution traces) associated with a specific AI contact. Each run log is returned as a full tree with its descendants, ordered from the most recent root run to the oldest. Use this endpoint to inspect what the AI did during a conversation: which assistants were used, which tools were called, what predefined behaviours triggered, and the input/output of each step.Use Cases
- Debug Assistant Behaviour: Inspect tool calls, context retrieval, and decisions step-by-step
- Audit & Compliance: Build an audit trail of AI actions taken per contact
- Analytics: Compute per-contact metrics about AI runs, tool usage, latency
- Customer Support: Understand why the assistant replied in a certain way to a given contact
Authentication
This endpoint requires authentication using an API key. Include your API key in the request header:x-api-key: your_api_key_here
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
ai_contact_id | string (UUID) | Yes | UUID of the AI contact whose run logs you want to retrieve |
page | integer | No | Page number (defaults to 1) |
page_size | integer | No | Items per page (defaults to 20, max 100) |
Response Structure
| Field | Type | Description |
|---|---|---|
page | integer | Current page number |
page_size | integer | Page size used to compute the response |
total | integer | Total number of root run logs for the contact |
run_logs | array | Array of root run logs, each containing nested children[] |
Run Log Object
| Field | Type | Description |
|---|---|---|
id | string (UUID) | Run log unique identifier |
run_type | string | Type of run (e.g. master, tool_call, predefined_behaviour, context) |
status | string | One of pending, running, success, failed |
content | object | null | Type-specific payload (inputs/outputs, parameters, etc.) |
error | object | null | Error details if the run failed |
start_time | string (ISO) | Timestamp when the run started |
end_time | string (ISO) | Timestamp when the run finished (null if still running) |
ai_contact_id | string (UUID) | AI contact this run belongs to |
parentId | string | null | Parent run log id (null for root run logs) |
children | array | Child run logs (recursively, same shape) |
Example Request
curl -X GET "https://api.vambe.me/api/public/run-logs?ai_contact_id=df980fc8-b6db-4820-bf22-2969482d106d&page=1&page_size=20" \
-H "x-api-key: your_api_key_here"
Error Responses
| Status Code | Description |
|---|---|
| 400 | Bad Request - Invalid ai_contact_id format |
| 401 | Unauthorized - Invalid or missing API key |
| 404 | Not Found - AI contact does not exist |
| 500 | Internal Server Error - Something went wrong |
Headers
API key required to authorize the request
Query Parameters
UUID of the AI contact to fetch run logs for. Mutually exclusive with voice_call_id.
Pattern:
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Id of the voice call to fetch run logs for. Mutually exclusive with ai_contact_id. Not necessarily a UUID: it falls back to the provider conversation id when the call was placed without one.
Minimum string length:
1Page number (defaults to 1)
Required range:
-9007199254740991 <= x <= 9007199254740991Page size (max 100; defaults to 20 by contact, 50 by voice call)
Required range:
-9007199254740991 <= x <= 9007199254740991Response
Run logs retrieved successfully.
Was this page helpful?