ObservabilityLogs

API request logs

Inspect logged Vapi API requests and their responses

The API tab shows requests recorded after they reached Vapi’s API logging layer, along with their stored request and response details. Use it to investigate logged requests from scripts and integrations.

Requests rejected before request logging, such as some authentication or authorization failures, might not appear. The API tab is therefore not a complete record of every request attempted against the Vapi API.

New to the API? See the API reference for endpoints and schemas. See API keys for creating and scoping keys. This page is about reading the request logs.

Access API request logs

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

The API request list

The API tab lists logged requests, most recent first. Each row shows:

  • Timestamp: when the request reached Vapi’s API logging layer.
  • Resource: the API resource the request targeted, such as assistant, phone-number, tool, or squad.
  • Request duration: how long Vapi took to respond, in seconds.
  • Request HTTP method: the method used, such as GET, POST, PATCH, or DELETE.
  • Response HTTP code: how the API responded. A 2xx code generally indicates success, while a 4xx or 5xx code indicates an unsuccessful response. Some endpoints use an expected redirect, such as the 302 returned when downloading call logs.

Use the search box to narrow the visible rows to the resource, method, or response code you are investigating.

API request logging has no separate enable or disable switch, and the assistant’s Logging setting does not control it. See Retention and logging configuration for availability and compliance behavior.

Opening an API request log

Select a request to open its 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. The Authorization header and other sensitive headers are excluded. Sensitive body values can be redacted.
  • Response: the HTTP code and response body when captured.
  • Miscellaneous: any stored error and the organization ID.

Debug with API request logs

Reach for the API tab when a request did not do what you expected:

  • A logged request returned an error. Start with the response code. A 400 can indicate an invalid request body, a 404 can indicate a wrong endpoint or resource ID, and a 5xx indicates a server-side failure. Check the endpoint’s API reference for its expected schema and responses.
  • A rejected request is not listed. Authentication, authorization, rate limiting, and routing checks can reject a request before it reaches request logging. Use the response returned to your client, then check your API key, endpoint, and request configuration.
  • Confirm the stored request details. Compare the method, path, query, selected non-sensitive headers, and captured body against what your code intended to send. The log is a sanitized representation, not an exact copy of the request.
  • Tie a request to a resource. Use the Resource column and the stored request path, query, or body to identify the endpoint and resource involved.