Recordings Overview

Recordings capture call audio for review and AI processing. Customer routes let you start and stop recording for a call, list recordings for a call, and retrieve recording metadata.

Integration checklist

Use recording controls only when your application needs the audio later for review, transcription, or quality workflows. Start recording at a clear point in the call flow, store the recording ID from responses or webhooks, and wait for the final call state before assuming the file is ready for downstream processing.

For testing, place a short call with known spoken phrases, then verify that your application can connect the call ID, recording ID, and later AI result. Also test a call with no recording so your UI has a clean empty state.

Copy/Paste Examples

Real Request

curl -sS -X POST https://api.minivoice.eu/v1/calls/call_123/recordings \
  -H 'Authorization: Bearer $MINIVOICE_API_KEY' \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "action": "start"
}
JSON

Real Response

{
  "data": {
    "call_id": "call_123",
    "action": "start",
    "recording": {
      "id": "rec_call_123",
      "status": "started",
      "duration_seconds": 0,
      "size_bytes": 0
    }
  }
}

Real Webhook Example

{
  "event": "call.completed",
  "created_at": "2026-05-29T12:10:00Z",
  "call": {
    "id": "call_123",
    "customer_id": "cust_123",
    "application_id": "app_123",
    "status": "completed",
    "direction": "inbound",
    "from": "+15551230001",
    "to": "+15551230002"
  },
  "variables": {},
  "data": {}
}

Common Use Case

Start and stop recording around the part of the call you need to review.

Common Failure Case

{
  "error": {
    "code": "recording_not_started",
    "message": "recording is not currently started"
  }
}

Use the error code for branching and log the full response body while testing.