Critical Webhook Issue Vapi AI #support

Critical Webhook Issue

Nate

11/10/2025, 9:49 PM

Hi Vapi Team, I'm experiencing a critical issue where webhook configurations are not being applied to new calls, despite being correctly configured at the assistant level. Issue Summary: New calls have

server.url: NOT SET

in the call object, meaning webhooks never fire, even though the assistant is properly configured. Problem: When I make test calls, the call objects show: ```json { "server": null, "serverUrl": null } What I've Tried: 1. Set webhook on assistant level (both serverUrl and server object) 2. Set webhook on phone number level 3. Removed phone number webhook to force inheritance from assistant 4. Updated serverMessages to include multiple event types 5. Verified backend endpoint is accessible and working Expected Behavior: New calls should inherit server.url from the assistant configuration and fire webhooks to the configured endpoint. Actual Behavior: Calls have no webhook configuration at all, webhooks never fire. Request: Can you investigate why the assistant's webhook configuration is not being applied to new calls on this assistant/phone number? Thank you for your help.

Vapi Support Bot

11/10/2025, 9:50 PM

To ensure your assistant's webhook is applied, explicitly set the server URL at the assistant level using the API as shown below:

Copy code

json
{
  "server": {
    "url": "https://your-server.com/webhook",
    "credentialId": "optional-auth-id"
  }
}

After updating, verify that the phone number's server URL is unset, as it will override the assistant's configuration if present. For more details, see the [Setting server URLs documentation](https://docs.vapi.ai/server-url/setting-server-urls). Source: - [Setting server URLs](https://docs.vapi.ai/server-url/setting-server-urls)

Nate

11/10/2025, 9:52 PM

already have done this.

Nate

11/10/2025, 9:52 PM

@User

kyle

11/10/2025, 11:32 PM

please also send the call id

Nate

11/17/2025, 4:00 AM

Copy code

We're not receiving end-of-call-report webhooks despite configuration being correct.

  Details:
  - Assistant ID: 35e8e102-d9b3-429f-8aeb-b0ff009d86ea
  - Org ID: 54c5b2c8-df9c-4fd1-a6f8-53fb439d3bcc
  - Call ID (test): 019a8feb-5a07-755a-8f08-56e31c882c39
  - Call ended: 2025-11-17T03:47:02Z
  - Ended reason: customer-ended-call

  Configuration verified via API:
  {
    "serverUrl": "https://api.gettruvo.com/webhook/vapi",
    "serverMessages": ["end-of-call-report"]
  }

  What we see:
  - Call completed successfully
  - Analysis generated (summary + structuredData present)
  - Webhook endpoint is live and accepting POST requests
  - No webhook received at our server (call not in our database)

  Endpoint test (works):
  curl -X POST https://api.gettruvo.com/webhook/vapi \
    -H "Content-Type: application/json" \
    -d '{"test": true}'
  # Returns: {"error":"Invalid webhook payload"} ← executes correctly

  Questions:
  1. Can you check if the webhook was attempted for call 019a8feb-5a07-755a-8f08-56e31c882c39?
  2. If attempted, what was the response/error?
  3. Is there a delivery status dashboard we can monitor?
  4. Are there known delays or retry policies we should account for?

  We re-patched the assistant config to ensure serverMessages is active, but the issue persists.

Nate

11/17/2025, 4:00 AM

@User please advise, ongoing issue...

Nate

11/18/2025, 7:10 PM

Chiranjeet Mishra

11/19/2025, 1:41 AM

Use this:

Copy code

curl -X PATCH https://api.vapi.ai/assistant/35e8e102-d9b3-429f-8aeb-b0ff009d86ea \
     -H "Authorization: Bearer " \
     -H "Content-Type: application/json" \
     -d '{
  "server": {
    "url": "https://api.gettruvo.com/webhook/vapi",
    "timeoutSeconds": 120
  }
      "serverMessages": "end-of-call-report"
}'

Previous Next