API call reports not consistent
# support
s
Do you all update the call report post hoc after a call? My call times from get call api are not consistent with call times for the same call when i call the api now. this is the case with all calls. what is happening?
v
@Sangy Yes, call reports can be updated post hoc after a call. This is typically done to ensure that the call summary data is accurate and reflects any changes or additional information that may have been gathered after the call ended. Regarding the inconsistency you're experiencing with call times, it's possible that there may be a delay in the system updating the call report with the final call times, or there could be a discrepancy due to time zone differences or system errors. If you're noticing that this inconsistency is happening with all calls and it's affecting your operations, I would recommend reaching out to support for a more detailed investigation into the issue. They can provide specific insights into why the call times might not be aligning and help resolve any potential problems with the data reporting.
You can continue this conversation by mentioning me in the message.
s
here is what i mean. this is data saved from the a call report after a call from the Get Call api (https://api.vapi.ai/call/{call_id}). this is not the end of call report. plotting cost vs duration, clearly the data is corrput. calling teh same endpoint nw is returning different call start and end times. what is happening? https://cdn.discordapp.com/attachments/1269138196701122683/1269144170304503868/image.png?ex=66aefe1d&is=66adac9d&hm=0dab5075e595c89cbfe179b54a6c9f1c85bb8852bf3a11039def8c25ec52b658&
c
what specifically is not adding up? Plotting cost and duration of call only? Also do you not have this in graph? You still have the numbers side by side? (Spreadsheet)
I ill start paying more attention to this this week. But my n umbers usually match up. For sure duration is the same because I had a hard time converting both those in my automation. I assume plotting cost is the tokens and etc.
s
what's not matching is the start and end times. for example: call id: "36ffba7c-a5d2-4ac6-b429-efd59877ce74" after the call, i call the call report and it returned: startedAt: "2024-07-15 07:12:19.894877+00". endedAt: ""2024-07-15 07:12:31.422479+00"" Cost - $1.002 this itself is a red flag as its $1 for a 10 sec call now, the startedAt time for the same call - "startedAt": "2024-07-15T07:04:42.156Z", "endedAt": "2024-07-15T07:12:08.080Z", "cost": 1.0022, why are the times not matching? same call, same API.
@Shubham Bajaj icymi, this can lead to a lot of accounting and reporting errors!
costs are lining up, the times are not
s
a call report is sent right after the call is hangup which includes the approximate real time duration whereas /call is supposed to be used after 30 seconds of call hangup to get absolute values.
s
as i said, im not using the end of call report thats send to server url. is the call api also not accurate after call finishes?
s
you have to wait for 30 seconds to let all processing after call hangs up to get finished.
s
ok. thanks.
2 Views