Call ID: 019b987f-1cc8-7339-ac46-b6bb403444d5 Timestamp: 2026-01-07 12:47:06.618 GMT Call ended successfully with endedReason: "assistant-said-end-call-phrase" All other server messages delivered end-of-call-report enabled but never attempted Full call data available via API are there any issues with end-of-call-report being triggered even though configured properly via assistant? All other webhooks being triggered.

Since the

end-of-call-report

webhook should be triggered automatically when a call ends, and all other webhooks are working, try testing your endpoint directly using a tool like

curl

to ensure it accepts POST requests with the expected payload. For example:

bash
curl -X POST https://your-server.com/webhook \
  -H "Content-Type: application/json" \
  -d '{"message": {"type": "end-of-call-report", "endedReason": "assistant-said-end-call-phrase"}}'

If your endpoint responds correctly, gather the Call ID and timestamp, then contact Vapi support for further investigation, as this may indicate a platform-side issue. For more details, see the [Vapi server events documentation](https://docs.vapi.ai/server-url/events). Source: - [Vapi server events documentation](https://docs.vapi.ai/server-url/events)

Seems like the issue was something else related to how VAPI dashboard changes is handling configuration

I’ve checked our logs, and they show that the end-of-call report was successfully sent at 2026-01-07T12:49:21.892559479Z, with a success status. Could you please check your server logs around this timestamp to see if there were any issues capturing the report? Also, please let us know whether this issue occurs consistently or was limited to this specific call.