Good evening, I’m currently setting up an outbound calling system using HTTP requests on Make.com, integrated with VAPI. While the outbound calls are being initiated successfully, I’m facing a key issue: VAPI is not generating any logs for the calls made, and as a result, I am unable to receive any end-of-call reports, because there is no call log for VAPI to reference. I understand that Make.com has a dedicated VAPI module, but I chose to use custom HTTP requests to have more control over the process. Given this, I have a few questions: Is it expected behavior that VAPI does not log or report calls initiated via HTTP requests? Are there specific requirements or parameters that must be included in the request to ensure the call is logged? Is there a way to manually retrieve call logs or summaries through the VAPI API after the call ends? Any insight into why the calls are not being logged? Thank you

You can retrieve call data after a call ends using the VAPI API's GET /call/:id endpoint:

bash
curl -X GET 'https://api.vapi.ai/call/{callId}' \
-H 'Authorization: Bearer YOUR_API_KEY'

This returns complete call data including the transcript, recording URLs, and conversation messages. Source: - [Discord conversation about retrieving call data](https://discord.com/channels/1211482211119796234/1341440757189578782)

Message marked as helpful by @DR ANTAF! 🎉

what about the data and metadata that's what I want to get

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!