Rafael
10/22/2025, 1:53 PMVapi Support Bot
10/22/2025, 1:55 PMjs
app.use(express.json({ limit: '50mb' }));
app.use(express.urlencoded({ limit: '50mb', extended: true }));
Restart your server after making this change. This should allow your End of Call Report webhook to be received successfully.
Source:
- [Webhook error 413 solution](https://docs.vapi.ai/calls/call-queue-management)Chiranjeet Mishra
10/22/2025, 5:05 PMvapi listen command to forward webhooks to your local development server. Here's a quick guide to get started:
1. **Set up Tunneling**: You'll need a public URL to expose your local server, which vapi listen does not provide. Use a tunneling service such as ngrok:
bash
ngrok http 4242 # Assuming 4242 is your chosen port
2. **Start Vapi Listener**: Forward the webhooks to your app:
bash
vapi listen --forward-to localhost:3000/webhook
3. **Update Webhook URLs**: Go to your Vapi Dashboard and set your webhook URLs to the URL provided by your tunneling service (e.g., https://abc123.ngrok.io).
4. **Trigger Webhooks**: Initiate webhook events (e.g., make a call) and watch them flow through the tunnel to your server.
For a more detailed process, refer to the [local webhook testing guide](https://docs.vapi.ai/cli/webhook).
If you experience any issues, ensure your server is running on the specified port, your endpoint path matches your route, and there are no firewall blocks. You can also verify CLI authentication using vapi auth whoami.
For more advanced configurations or troubleshooting, visit the [custom tools troubleshooting guide](https://docs.vapi.ai/tools/custom-tools-troubleshooting).