### Answer
It sounds like you're encountering behavior related to how Vapi sends messages to your server URL during a call. Vapi communicates with your server URL via HTTP POST requests for various reasons, including status updates, function calls, and the end-of-call report [(1)](
) . The frequent messages you're receiving could be status updates or other intermediate messages rather than the end-of-call report.
The end-of-call report specifically is sent once the call ends, containing a summary, transcript, and other call details. This report is what you're seeing as the last call to your webhook. This behavior is expected as part of Vapi's operation to keep your server informed about the ongoing call's status and any relevant events.
If you're only interested in the end-of-call report, you may want to implement logic on your server or within your Make.com scenario to specifically handle or filter for these reports, ignoring intermediate messages if they're not relevant to your use case.