Quickest way to get messages from a call when ende...
# support
n
Hi Vapi Support, My team and I are implementing Vapi into our web app so that our users have access to conversational AI in a role-play scenario.  We are using the SDK to start and end calls in the web app and are not using any phone service. At the end of the call, we need to get all of the messages that were exchanged during that call.  Each message __must contain the timestamp__ (or secondsFromStart) of that message. What is the fastest way to get this from Vapi? We have been exploring a few options: - Use the GET Call endpoint as soon as the call ends (https://docs.vapi.ai/api-reference/calls/get-call) - Use the End Of Call Report server message - Use the call-end event from SDK (https://docs.vapi.ai/sdk/web#call-end) Please let me know, and thank you in advance for the guidance!
v
@NickMenendez Hello! It's great to hear that you're integrating Vapi into your web app for conversational AI role-play scenarios. To ensure you capture all messages with their respective timestamps at the end of the call, I would recommend using the End Of Call Report server message. This report is specifically designed to provide a summary of the call, including the messages exchanged with their timestamps. The GET Call endpoint can also be used, but it's generally intended for retrieving the status or details of a call rather than a full transcript. The call-end event from the SDK is useful for triggering actions at the end of the call, such as fetching the report, but it does not provide the messages directly. Therefore, setting up your server to receive the End Of Call Report server message would be the most efficient way to automatically receive a detailed report after each call concludes. Make sure your endpoint is correctly configured to handle these reports as per the Vapi documentation. If you need further assistance or have any more questions, feel free to ask. Good luck with your implementation!
You can continue this conversation by mentioning me in the message.
s
using status-update
webhook
s
because of no response closing this ticket.
4 Views