Retrieve Appointment Analysis — Shilo API

Use this endpoint to retrieve the AI-generated analysis for an appointment recording. Shilo processes each appointment asynchronously after ingestion, producing coaching feedback, a call rating, conversation summary, disposition outcomes, objection handling insights, and speaker identification. Because processing takes time, you should poll this endpoint and check the progress field — results are only fully available once progress reaches 100.

Endpoint

GET https://api.shilo.ai/api/v1/appointments/{identifier}/analysis

Authentication

All requests require your API key in the x-api-key header.

Path Parameters

string

required

The unique identifier for the appointment recording. Two formats are accepted:

{uuid} — The Shilo recording UUID (e.g., ee6f2136-b94a-4438-9335-3acf5b2a0d31)
external_recording_id:{string} — The external recording ID your integration provided (e.g., external_recording_id:ext-789)

Response

A successful request returns HTTP 200 with a RecordingAnalysis object. The top-level fields id, recording_id, created_at, and progress are always present. All sub-resource fields (coaching, rating, summary, etc.) are optional and only fully populated once progress equals 100.

string

required

The UUID of this analysis record.

string

required

The Shilo recording UUID of the appointment this analysis belongs to.

string

required

The ISO-8601 timestamp indicating when this analysis was created.

number

required

A value between 0 and 100 representing how far along the AI processing pipeline this recording is. Poll this endpoint until progress equals 100 before reading any result fields.

object

Recommended follow-up actions identified by the AI. Present only after processing completes.

Show action_items fields

string

The UUID of this action items record.

string[]

The most important follow-up actions for the rep to take after this appointment.

string[]

Additional, lower-priority follow-up actions.

object

AI-generated coaching feedback for the rep on this appointment. Present only after processing completes.

Show coaching fields

string

The UUID of this coaching record.

string[]

Areas where the rep could have performed better, with specific suggestions.

string[]

Highlights from the appointment where the rep performed particularly well.

object

The AI-assessed outcome and reasoning for this appointment. Present only after processing completes.

Show disposition fields

string

The UUID of this disposition record.

string[]

The determined outcome labels for the appointment (e.g., booked, not interested).

string

A plain-language explanation of why the AI assigned these outcomes.

object

Objections raised by the contact during the appointment. Present only after processing completes.

Show objections fields

string

The UUID of this objections record.

string[]

A list of objections identified in the conversation.

object

A numeric quality rating assigned to the rep’s performance on this appointment. Present only after processing completes.

Show rating fields

string

The UUID of this rating record.

number

The numeric rating score assigned to the rep’s performance.

string

A plain-language explanation of what drove the assigned score.

object

AI-resolved speaker identities for the appointment recording. Present only after processing completes.

Show speakers fields

string

The UUID of this speakers record.

string

The resolved name of the sales rep in this recording.

string

The resolved name of the client or contact in this recording.

object

A concise AI-generated summary of the appointment. Present only after processing completes.

Show summary fields

string

The UUID of this summary record.

object

An object containing the summary text.

Show outcome fields

string

The full text of the AI-generated appointment summary.

Poll this endpoint until progress equals 100 before reading result fields such as coaching, rating, or summary. Sub-resource fields are absent or incomplete until processing finishes.

Error Responses

Status	Description
`400 Bad Request`	The `identifier` path parameter is malformed or uses an unsupported format.
`404 Not Found`	No appointment recording was found matching the provided identifier.

Example Request

curl --request GET \
  --url "https://api.shilo.ai/api/v1/appointments/ee6f2136-b94a-4438-9335-3acf5b2a0d31/analysis" \
  --header "x-api-key: YOUR_API_KEY"

Example Response

{
  "id": "a1b2c3d4-0000-4000-8000-111122223333",
  "recording_id": "ee6f2136-b94a-4438-9335-3acf5b2a0d31",
  "created_at": "2030-09-24T12:40:00Z",
  "progress": 100,
  "action_items": {
    "id": "a1b2c3d4-0000-4000-8000-aaaaaaaaaaaa",
    "primary": [
      "Send follow-up email with pricing sheet",
      "Schedule a product demo for next week"
    ],
    "secondary": [
      "Add contact to nurture sequence"
    ]
  },
  "coaching": {
    "id": "a1b2c3d4-0000-4000-8000-bbbbbbbbbbbb",
    "possible_improvements": [
      "Slow down when presenting pricing to allow time for questions",
      "Ask more open-ended discovery questions early in the call"
    ],
    "top_moments": [
      "Excellent handling of the budget objection at the 12-minute mark",
      "Strong rapport-building during the opening"
    ]
  },
  "disposition": {
    "id": "a1b2c3d4-0000-4000-8000-cccccccccccc",
    "outcomes": ["demo_scheduled"],
    "reasoning": "The contact agreed to a product demo and expressed strong interest in the enterprise plan."
  },
  "objections": {
    "id": "a1b2c3d4-0000-4000-8000-dddddddddddd",
    "outcomes": [
      "Price is too high",
      "Need to involve another decision-maker"
    ]
  },
  "rating": {
    "id": "a1b2c3d4-0000-4000-8000-eeeeeeeeeeee",
    "outcome": 82,
    "reasoning": "The rep demonstrated strong product knowledge and handled objections confidently, with room to improve discovery questioning."
  },
  "speakers": {
    "id": "a1b2c3d4-0000-4000-8000-ffffffffffff",
    "user_name": "Jordan Smith",
    "client_name": "Alex Rivera"
  },
  "summary": {
    "id": "a1b2c3d4-0000-4000-8000-000000000000",
    "outcome": {
      "summary": "Jordan connected with Alex to discuss upgrading from the starter plan. Alex raised concerns about pricing and the need to consult a second decision-maker. Jordan successfully navigated both objections and secured commitment for a follow-up demo next Thursday."
    }
  }
}

Overview

Calls

Appointments

Roleplays

Contacts

Users

Invitations

Metrics

Coaching

Retrieve Appointment Analysis — Shilo API

Endpoint

Authentication

Path Parameters

Response

Error Responses

Example Request

Example Response

​Endpoint

​Authentication

​Path Parameters

​Response

​Error Responses

​Example Request

​Example Response

Endpoint

Authentication

Path Parameters

Response

Error Responses

Example Request

Example Response