WebHooks Errors - URGENT Vapi AI #support

WebHooks Errors - URGENT

julian

09/29/2025, 4:28 PM

Hey! There's any WebHook for Error, for example get-transports, quotas, etc...? Now only work for normal calls, but on errors dont send any.

Vapi Support Bot

09/29/2025, 4:29 PM

Vapi webhooks can forward
error
events, but these are typically related to call lifecycle or system-level issues, not general API errors like "get-transports" or quota limits. To handle error events in your webhook handler, you can filter for the

error

type:

Copy code

js
app.post('/webhook', (req, res) => {
  if (req.body.type === 'error') {
    // Handle error event here
    console.error('Vapi error event:', req.body);
  }
  res.status(200).send();
});

Currently, there is no documentation indicating that non-call-related errors (like quota or transport errors) trigger webhook events. For more details, see the [webhook event types documentation](https://docs.vapi.ai/cli/webhook). Source: - [Webhook Testing & Event Types](https://docs.vapi.ai/cli/webhook)

julian

10/02/2025, 8:21 PM

Or create a tool on fail, or something.

julian

10/06/2025, 4:42 PM

[{ "on": "call.ending", "filters": [{ "type": "oneOf", "key": "call.endedReason", "oneOf": ["pipeline-error", "start-error"] }], "do": [{ "type": "tool", "tool": { "type": "function", "server": { "url": "hook" }, "function": { "name": "report_error", "parameters": { "type": "object", "properties": { "text": { "type": "string", "value": "A call error occurred." } } }, "description": "Reports a call error to Slack." }, "async": True, "server": { "url": "hook" } } }] }] But Only reports pipeline-error, but start-error is registering nothing, like call.start.error-get-transport or something like that

julian

10/06/2025, 4:43 PM

@User @User

Chiranjeet Mishra

10/06/2025, 8:00 PM

Key Webhooks for Error Logging status-update - This is crucial for error logging as it includes: - Call status changes - endedReason field when calls end with errors - inboundPhoneCallDebuggingArtifacts for debugging failed calls end-of-call-report - Provides comprehensive call analysis including: - Complete call artifacts - Cost breakdown - Analysis results - Any errors that occurred during the call hang - Sent when the assistant is hanging due to delays, which can indicate: - Model response delays - Voice synthesis issues - Tool call timeouts - Network problems

julian

10/07/2025, 3:23 PM

The thing is : call.start.error-get-transport As ended reason doesn't trigger the webhook to the server url. This is only retrievable via VAPI API. How can i report this to the hook?

Operations📟

10/20/2025, 12:45 AM

Figured it out yet? same issue here

julian

10/31/2025, 3:59 PM

Nothing, we made a Frankenstein with the hooks and the API running each minute to being able to notify these errors 🥴

Operations📟

10/31/2025, 4:17 PM

I forget what my exact issue was with this, but I think the request URL I used was wrong:

Copy code

ansi
[2;31m https://api.vapi.ai/call/phone

instead of

Copy code

ansi
[2;32m https://api.vapi.ai/call/

Chiranjeet Mishra

11/03/2025, 9:45 PM

We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.

2 Views

Previous Next