worming
10/24/2025, 7:50 PMVapi Support Bot
10/24/2025, 7:51 PMjson
{
"server": {
"url": "https://your-api.com/webhook"
}
}
You can also set this in the Vapi Dashboard under your assistant's "Advanced" tab. This ensures your API receives the relevant call event webhooks.
Source: [Setting server URLs documentation](https://docs.vapi.ai/server-url/setting-server-urls)worming
10/24/2025, 7:52 PMChiranjeet Mishra
10/27/2025, 7:30 PMvapi listen command in combination with a tunneling service like ngrok. Here's a quick guide:
1. Start your local server:
- Ensure your application is running and listening on a port, for example localhost:3000/webhook.
2. Create a tunnel:
- Use ngrok to expose your localhost to the internet. Run:
bash
ngrok http 4242
- Note the public URL provided by ngrok (e.g., https://abc123.ngrok.io).
3. Start the webhook listener:
- Open a new terminal and execute:
bash
vapi listen --forward-to localhost:3000/webhook
4. Update your Vapi dashboard:
- Set your webhook URLs in the Vapi dashboard to the ngrok public URL.
5. Test:
- Trigger webhook events in your applications or Vapi console to see them routed to your local server through the tunnel.
Remember that vapi listen does not create a tunnel on its own, so ensure the tunneling service is running. For [detailed information, refer here](https://docs.vapi.ai/cli/webhook).worming
10/31/2025, 1:44 AMChiranjeet Mishra
11/03/2025, 8:58 PMworming
11/03/2025, 11:17 PMChiranjeet Mishra
11/05/2025, 9:51 PMstatus-update – Sent when the call status changes (e.g., started, in-progress, ended).
- Use this to detect when a call starts or ends.
2. end-of-call-report – Sent after the call finishes, containing full details like duration, transcript, and cost.
These two events together give you a full picture of the call lifecycle.
---