----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Glossary]() * [Server URLs]() * [Get Call]() * [List Calls]() -----------------------------

### Answer It appears there might be an issue with the webhook data not updating correctly in real-time, which could be affecting the cost data in the end-of-call report. This is a known issue where the call object sent in webhooks can be stale from the start of the call, and it may not reflect the most current data, including cost [(1)]() . To fetch the latest details, including the accurate cost of the call, you could use the

GET /call/:id

endpoint to retrieve the most current information directly from Vapi. Here's an example of how to fetch the call data using this endpoint:

curl
curl --request GET \
  --url https://api.vapi.ai/call/{id} \
  --header 'Authorization: Bearer <token>'

[(2)]() Ensure that you replace

{id}

with the specific call ID and

<token>

with your authorization token to get the accurate details from the server. This approach should provide the real-time cost and other updated information for the call.

prospect didn't pickup

added 60 second delay, still comes through as 0

and give it a try

ill test.

Which will not be stale.

worked

thank you for being helpful