For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
WebsiteStatusSupportDashboard
DocumentationAPI ReferenceMCPSDKsCLI (new)What's New?
DocumentationAPI ReferenceMCPSDKsCLI (new)What's New?
  • Get started
    • Introduction
    • Phone calls
    • Web calls
    • Vapi Guides
    • Composer
    • CLI quickstart
  • Assistants
    • Quickstart
    • Tools
    • Custom keywords
    • Custom voices
    • Custom transcriber
    • Custom TTS
  • Observability
    • Boards
  • Squads
    • Quickstart
    • Overview
    • Handoff tool
    • Passing data between assistants
  • Best practices
    • Prompting guide
    • Debugging voice agents
    • Enterprise environments (DEV/UAT/PROD)
    • IVR navigation
  • Phone numbers
    • Free Vapi number
    • Inbound SMS
    • Phone Number Hooks
  • Calls
    • Call end reasons
    • Troubleshoot call errors
  • Outbound Campaigns
    • Quickstart
    • Overview
  • Chat
    • Quickstart
    • Streaming
    • Non-streaming
    • OpenAI compatibility
    • Session management
    • Variable substitution
    • SMS chat
    • Web widget
    • Webhooks
  • Workflows
    • Quickstart
    • Overview
      • FAQ
      • Support
        • Data flow
        • JWT authentication
        • Recording consent plan
        • GDPR compliance
        • HIPAA compliance
        • Retrieve call artifacts
        • PCI compliance
        • Proxy server guide
        • Static IP addresses
        • SOC-2 Compliance
LogoLogo
WebsiteStatusSupportDashboard
On this page
  • Overview
  • Get your Private API Key
  • Integration
  • Available endpoints
  • Example
ResourcesSecurity and privacy

Retrieve call artifacts

Download recordings and call logs from Vapi’s private storage using authenticated, short-lived URLs.

Was this page helpful?
Edit this page
Previous

PCI Compliance

Ensure secure payment data handling while using Vapi’s voice assistant platform.

Next
Built with

Overview

For HIPAA-enabled organizations, call recordings and logs are stored in a private bucket. These URLs are not directly downloadable.

To retrieve a recording or log file, call the Vapi API with your Private API Key. The API responds with a 302 redirect to a short-lived, authenticated download URL.

Never expose your Private API Key in client-side code or commit it to version control. Store it as a secret in your backend environment.

Get your Private API Key

  1. Open the Vapi Dashboard.
  2. Go to Manage → API Keys.
  3. Copy the value of your Private API Key.

Integration

To download or retrieve a recording or log file, send your Private API Key in the Authorization header:

Authorization: Bearer <PRIVATE_API_KEY>

Each endpoint responds with a 302 redirect to a short-lived signed URL. Most HTTP clients follow redirects by default — for example, curl -L follows the redirect and downloads the artifact in a single command.

Available endpoints

Base URL: https://api.vapi.ai

EndpointReturns
GET /call/{id}/mono-recordingCombined mono recording (WAV/MP3)
GET /call/{id}/stereo-recordingStereo recording, customer + assistant on separate channels (WAV/MP3)
GET /call/{id}/customer-recordingCustomer-only mono recording (WAV/MP3)
GET /call/{id}/assistant-recordingAssistant-only mono recording (WAV/MP3)
GET /call/{id}/video-recordingVideo recording, when enabled (MP4)
GET /call/{id}/call-logsStructured call logs (gzipped JSONL)
GET /call/{id}/pcapPacket capture, when enabled (PCAP)

Example

Download a stereo recording for a given call:

$curl -L \
> -H "Authorization: Bearer $VAPI_PRIVATE_API_KEY" \
> -o recording.wav \
> https://api.vapi.ai/call/<CALL_ID>/stereo-recording

Download call logs:

$curl -L \
> -H "Authorization: Bearer $VAPI_PRIVATE_API_KEY" \
> -o call-logs.jsonl.gz \
> https://api.vapi.ai/call/<CALL_ID>/call-logs

Signed URLs returned by these endpoints expire after a short period. Always request a fresh URL from the API rather than caching the redirect target.