Logs overview

Find the right log for what you need to know

The Logs section of the Dashboard brings together retained activity across five tabs:

  • Calls: voice calls, including transcripts, messages, recordings, analysis, latency, and cost when available.
  • Chat: text conversations with an assistant.
  • Sessions: conversation state that persists across chats.
  • Webhooks: logged server-message delivery operations from Vapi to your server.
  • API: requests logged by the Vapi API.

Retention and logging configuration

Log generation, history availability, and data deletion are separate controls. An activity must happen before Vapi can log it. What remains available then depends on your subscription, compliance mode, and any settings for that log type.

Usage only and each Success Package determine how far back history is available in Vapi. The Extended Retention add-on can raise the call and chat history windows. Calls use the call-history window, Chat and Sessions use the chat-history window, and Webhooks and API use the longer of the two. See Pricing and Success Packages.

The separately billed Data Retention add-on enables an organization setting that clears eligible call, chat, and session content after the configured number of days. It does not delete Webhook or API logs. See Manage Success Packages and add-ons.

Compliance settings can also change what Vapi stores:

  • ZDR: For calls, Zero Data Retention (ZDR) prevents Vapi from storing recordings, transcripts, messages, summaries, and detailed pipeline logs. Call records and limited operational data, including cost and performance metrics, remain available. ZDR also prevents Vapi from storing Webhook and API request logs.
  • HIPAA: HIPAA mode uses HIPAA-compliant storage for supported call logs, recordings, and transcripts. API and Webhook logs use the HIPAA log store when HIPAA with Data Retention is enabled. Configured retention and artifact settings still apply.

ZDR and HIPAA mode cannot be enabled together.

SurfaceDo you need to enable logging?What configuration affects it?
CallsNo. Vapi creates the call record automatically.Logging, Audio Recording, and Transcript are enabled by default and controlled separately under Assistants → Advanced → Recording & Artifacts. Logging controls detailed pipeline logging, not the call record.
ChatNo. Chat logging has no separate enable or disable switch.For chats that Vapi stores, the subscription’s chat-history window limits how long the record remains available.
SessionsNo. Session logging has no separate enable or disable switch.For sessions that Vapi stores, the chat-history window limits how long the record remains available. Session expiration controls how long a session remains active, not how long its history is available.
WebhooksNo. Vapi creates a log when it attempts a configured server-message delivery.Your Server URL and event configuration determine which deliveries happen. The assistant’s Logging setting does not disable Webhook-tab logs. ZDR prevents the log from being written; the subscription log-history window limits how long written logs remain available.
API requestsNo. Vapi automatically logs requests that reach its API logging layer.There is no separate switch, and the assistant’s Logging setting does not control this log type. Requests rejected before the logging layer might not appear. The subscription log-history window limits availability; ZDR prevents Vapi from writing API request logs.

Which log answers which question

You want to…Look in
See what happened on a phone or web callCall logs
Review a text conversationChat logs
Understand why a conversation lost contextSession logs
Review a logged server-message deliveryWebhook logs
Inspect a logged API request and responseAPI request logs

Filter and find

Use the search and filters available on each tab. Calls, Chat, Sessions, and Webhooks support time-range filtering and log-specific filters. The API tab supports text search.

Access logs

The Dashboard provides all five log types. Calls, chats, and sessions also have public resource endpoints.

SurfaceDashboardPublic API
Call logsLogs → CallsList calls / Get call
Chat logsLogs → ChatList chats / Get chat
Session logsLogs → SessionsList sessions / Get session
Webhook logsLogs → WebhooksNo Logs endpoint
API request logsLogs → APINo Logs endpoint