VAPI•2mo ago

Status update sent without subscribing to it.

The status-update package is being sent to my webhook without asking for it. Im only requesting the end-of-call-report. This is happening accross all my assistants and organization and causing problems on the webhook side.
This is what im requesting. Is there a way to BLOCK the status updates via patch?
thnx

],
"serverMessages": [
"end-of-call-report"
],

Vapi Support BotAPP•11/5/25, 9:38 PM

Currently, there is no documented way to block or disable status-updatestatus-update messages via a PATCH or configuration change—even if you only specify "end-of-call-report""end-of-call-report" in your serverMessagesserverMessages array.
If this behavior is causing issues, the best next step is to contact Vapi support or monitor the Server Events documentation for updates.

"serverMessages": [
  "end-of-call-report"
]

"serverMessages": [
  "end-of-call-report"
]

This configuration does not guarantee suppression of status-updatestatus-update messages based on current documentation.

Source:

Server Events documentation

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

dangerous-fuchsiaOP•11/7/25, 5:37 PM

@Vapi Team

KyleAPP•11/7/25, 8:47 PM

You can restrict your assistant to only send the

end-of-call-report

end-of-call-report

by updating the assistant configuration with a PATCH request and explicitly defining the allowed server messages.

Use a PATCH like this to the /assistant endpoint:

{
  "serverMessages": ["end-of-call-report"]
}

{
  "serverMessages": ["end-of-call-report"]
}

This will ensure that only the end-of-call report is delivered to your webhook, and other server messages — including status-updatestatus-update — will no longer be sent.

If you run into any issues after patching, feel free to share the assistant ID and I can double-check the configuration.

dangerous-fuchsiaOP•11/14/25, 1:48 AM

In theory my assistants are already patched that way (and only showing the end of call report in server messages when I pull the assistant with postman, but they also send other update messages to the webhook (not only the end of call reports). For example:

Assistant e330efe4-6a0e-4172-8667-ed06e7bfad9e is patched.

But a this timestamp: 1763080291890
it sent :
"message": {
"timestamp": 1763080291890,
"type": "status-update",
"status": "ended",
"endedReason": "customer-busy",
"call": {
"id": "019a7fc6-3e64-711c-a3a4-4edfd98b2afe",
"assistantId": "29db80f0-304d-4b7d-b5bf-bd2a3dfb4ea5",
"customerId": null,
"type": "outboundPhoneCall",
"startedAt": null,
"endedAt": null,
"transcript": null,
"recordingUrl": null,
"summary": null,
"createdAt": "2025-11-14T00:31:29.892Z",
"updatedAt": "2025-11-14T00:31:31.497Z",

etc etc

And when i get the assistant json in postman, for the server messages part i only see:

"clientMessages": [
"transcript"
],
"serverMessages": [
"end-of-call-report"
],
"endCallPhrases": [],............. etc

How can i make it to only send the end of call report and not reports for voicemails, bussy numbers etc etc? @Vapi Team

KyleAPP•11/17/25, 11:44 PM

Hi there,

Currently, if you have the end-of-call report webhook enabled, Vapi will automatically send an EOC report for all endCallReasons. This includes cases like voicemail, customer-busy, and other non-connected outcomes.

As a workaround, you can filter these on your side after the webhook reaches your server. Simply ignore or discard events where the endedReason is voicemail or customer-busy, and only process the ones you care about.

Status update sent without subscribing to it.

Similar Threads

Similar Threads

Similar Threads