Activity Logs

Overview

Use this endpoint to audit call-related actions, including tool calls, end-call webhook delivery, and inbound context lookups.

Endpoint

• URL: /logs
• Method: GET
• Authentication: Required

Request

Query Parameters

Parameter	Type	Required	Default	Description
log_type	string	No	—	Filter by tool_call, end_call_webhook, or inbound_context_lookup.
assistant_id	string	No	—	Filter by assistant ID.
room_name	string	No	—	Filter by room name.
page	integer	No	1	Page number.
limit	integer	No	50	Page size (max 100).

Response Schema

Field	Type	Description
success	boolean	Operation status.
message	string	Result message.
data.logs	array	Activity log list.
data.logs[].log_type	string	tool_call, end_call_webhook, or inbound_context_lookup.
data.logs[].status	string	success or error.
data.logs[].assistant_id	string	Assistant identifier.
data.logs[].room_name	string	LiveKit room name for the call.
data.logs[].timestamp	string	UTC timestamp.
data.logs[].message	string	Human-readable log summary.
data.logs[].request_data	object	Outbound payload details.
data.logs[].response_data	object	Received response payload.
data.logs[].latency_ms	integer	Request round-trip latency in milliseconds.
data.total	integer	Total matching records.
data.page	integer	Current page number.
data.limit	integer	Current page size.

HTTP Status Codes

Code	Description
200	Logs returned successfully.
401	Unauthorized (invalid or missing API key).
500	Internal server error.

Example Request

curl -X GET "https://api-livekit-vyom.indusnettechnologies.com/logs?page=1&limit=20" \
  -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
  "success": true,
  "message": "Activity logs fetched successfully",
  "data": {
    "logs": [
      {
        "log_type": "inbound_context_lookup",
        "status": "success",
        "assistant_id": "550e8400-e29b-41d4-a716-446655440000",
        "room_name": "550e8400_abc123",
        "timestamp": "2026-03-10T09:15:42.000Z",
        "message": "Inbound context lookup completed successfully",
        "request_data": {
          "strategy_id": "f0f6d398-f9d9-4a7b-bc8e-4f24f57ec2de",
          "strategy_type": "webhook",
          "url": "https://example.com/caller-context",
          "payload": {
            "caller_number": "+919876543210",
            "inbound_number": "918044319240"
          }
        },
        "response_data": {
          "context_keys": ["customer_name", "ticket_id"],
          "context_size": 2
        },
        "latency_ms": 312
      }
    ],
    "total": 1,
    "page": 1,
    "limit": 20
  }
}

Inbound Context Lookup Log Behavior

inbound_context_lookup logs are created only when:

• The call is inbound.
• The inbound mapping has inbound_context_strategy_id.
• A lookup is attempted by the worker.

Success logs usually include:

• strategy/request details
• status and latency
• summary fields like returned context keys

Error logs usually include:

• timeout, HTTP failure, invalid JSON, or invalid response shape details
• status and latency

Lookup failures are observable in logs but do not block the call. The assistant still starts with default prompt behavior.

Notes

• Results are always scoped to the authenticated user.
• Logs are returned in descending timestamp order.