Submit Call Recordings for AI Analysis with Shilo

Shilo’s call submission endpoint accepts a recording URL and associated metadata, queues the call for AI processing, and returns a call_event_id you can use to poll for results. The entire pipeline is asynchronous—your system receives an immediate 202 Accepted response, and Shilo handles the transcription, speaker resolution, and AI analysis in the background.

Overview

Endpoint: POST /api/v1/calls
Authentication: Read-write API key required
Response: 202 Accepted with call_event_id and status: "QUEUED"

Error Responses

Status	Meaning	Resolution
`400 Bad Request`	The request body is missing required fields or contains invalid values	Check the error message for which field failed validation
`403 Forbidden`	Your API key is read-only	Use a read-write API key for this endpoint
`401 Unauthorized`	The API key is missing or invalid	Verify the `x-api-key` header and key value

AI Model Overrides

If your Shilo plan supports custom AI models, you can override the model used for specific analysis types by including the ai_models array:

{
  "ai_models": [
    { "type": "coaching", "model": "custom_coaching_model_v2" }
  ]
}

Contact your Shilo account manager for available model identifiers.

⌘I

Get Started

Core Concepts

Guides

Submit Call Recordings for AI Analysis with Shilo

Overview

Error Responses

AI Model Overrides

​Overview

​Error Responses

​AI Model Overrides

Overview

Error Responses

AI Model Overrides