auto_start_meeting_summary is not reflected via API (PATCH returns 204, but the value remains false)

Meeting SDK
1

Hello Zoom Support Team,

I hope you are doing well.

I am reaching out to confirm an issue we are seeing in our integration using the Zoom API with Server-to-Server OAuth. Specifically, the automatic start setting for Meeting Summary does not seem to be applied.

Issue

Target setting: settings.auto_start_meeting_summary

We send the following request to PATCH /v2/meetings/{meetingId}:

{
  "settings": {
    "auto_start_meeting_summary": true
  }
}

The API response returns HTTP 204 (success).

However, when we immediately call GET /v2/meetings/{meetingId} afterward, settings.auto_start_meeting_summary still remains false.

Impact

We are able to receive the meeting.started webhook successfully, so webhook delivery itself is working correctly.

However, meeting.summary_completed is never triggered.

Because of this, our automatic meeting summary retrieval flow cannot be completed.

Environment

  • App Type: Server-to-Server OAuth (Account-level app)

  • Event Subscriptions:

    • meeting.started

    • meeting.summary_completed

  • Required scopes have already been granted (including read/update/past instances, etc.)

Steps to Reproduce

  1. Obtain an S2S OAuth access token

  2. Send the following request to PATCH /v2/meetings/{meetingId}:

{
  "settings": {
    "auto_start_meeting_summary": true
  }
}

  1. Confirm that the response is HTTP 204

  2. Call GET /v2/meetings/{meetingId} to verify the setting value

Result:

auto_start_meeting_summary = false

Example Meeting ID

81017348930

Questions

Could you please confirm the following points?

  1. Is auto_start_meeting_summary a setting that can be reliably configured via the API (create/update)?

  2. Are there any restrictions depending on the meeting type (for example, recurring / no fixed time) or account-level conditions that would cause this setting to be ignored?

  3. Is there any known issue where the PATCH request returns HTTP 204 but the setting is not actually applied?

  4. Are there any additional requirements for meeting.summary_completed to be triggered?

If needed, we can also provide the actual request/response headers, timestamps, and tracking IDs.

Thank you for your time and support.

2

Hi @beaute_eternelle
Thanks for reaching out to us! I am happy to help here!
This issue could be due to the account settings you might have.
Make sure to go to your Settings → AI companion → Meeting summary with AI companion and make sure the toggle is on

1 Like
3

Thank you! All cleared!