ObservabilityLogs

Webhook logs

Inspect server-message delivery results and debug failed deliveries

Webhook logs show recorded server-message delivery operations from Vapi to your Server URL and the final result of each operation. Use the Webhooks tab to confirm a logged delivery and investigate unsuccessful outcomes.

New to server messages? See Server events for the event types Vapi sends. See Server authentication to secure the endpoint. This page is about reading the delivery logs.

Access webhook logs

  • Dashboard: Logs → Webhooks
  • API: No Logs endpoint. Use the Dashboard to view webhook logs.

The webhook list

The Webhooks tab lists each logged delivery operation with:

  • Timestamp: when Vapi started the delivery.
  • Webhook type: the delivery type, such as end-of-call-report or tool-calls. See Server events for server-message types.
  • Request HTTP method: how Vapi called your server (usually POST).
  • Response HTTP code: the final result of the delivery. Any 2xx response means your server accepted it; a non-2xx result means the delivery did not succeed.
  • Request duration: the total elapsed time for the delivery operation. This can include retries and the time between them.

Filter by time range, HTTP method, response code, webhook type, assistant, squad, phone number, call ID, or webhook log ID.

Vapi writes a Webhook log when it attempts a configured server-message delivery. See Retention and logging configuration for configuration, availability, and compliance behavior.

Opening a webhook log

Select a delivery to open its Webhook Details, organized into three tabs:

  • Request: stored request details, including the method, URL, path, query, selected non-sensitive headers, request body when captured, and timing information. Authentication headers and other sensitive headers are excluded. Sensitive body values can be redacted.
  • Response: the final HTTP code and response body when captured.
  • Miscellaneous: any captured error and the available identifiers for correlating the delivery, such as call, assistant, squad, phone number, and customer IDs.

Debug with webhook logs

Reach for webhook logs when your server did not act on an event:

  • The response is 401 or 403. Your server may have rejected the request’s authentication. Check the response and any error under Miscellaneous.
  • The response is 404. Verify the Server URL and path.
  • The response is 5xx, or the duration is long. A 5xx result can come from your server or from a transport or timeout failure. A long duration can indicate retries or a timeout, but does not prove either one by itself.
  • Confirm the stored request details. Inspect the method, URL, selected non-sensitive headers, and body captured in the Request tab. Authentication headers and other sensitive headers are excluded. Verify the authentication values against your server authentication configuration.
  • Tie a delivery to its call. When available, the Miscellaneous tab includes the call, assistant, and squad IDs you can use to find the matching call log.
  • An event seems missing. Filter by webhook type and call ID. A missing log does not prove that Vapi made no delivery attempt because retention and ZDR settings affect which logs are stored.