I’d treat these as two separate paths, not one webhook issue. RTMS transcript working only proves the RTMS connection and transcript scope are good. It does not prove chat support as Chun already mentioned is not live yet and is still on the roadmap.
For the current in-meeting chat webhook path, the blocker is likely enablement, not code. Zoom exposes the meeting.chat_message_sent event separately from RTMS, and Zoom ties in-meeting chat capture to in-meeting chat DLP. So scopes and event subscription setup are necessary, but they are not enough if DLP and the app-level event are not enabled by Zoom.
The next practical step is to ask Zoom Support to enable in-meeting chat DLP for the account. After enablement, send one public in-meeting chat message and check the app’s Event Subscriptions delivery logs.
The selected event is Meeting → In-meeting chat message received.
The app has the RTMS chat scope meeting:read:meeting_chat.
RTMS webhook events and live transcript callbacks are reaching the same endpoint successfully.
Zoom’s Events dashboard shows 0 webhook event calls for in-meeting chat after sending chat messages in a test meeting.
My server logs also show no incoming chat webhook POSTs, so the issue appears to be that Zoom is not emitting the event, not that my endpoint is rejecting it.
Can someone from Zoom confirm whether In-meeting chat message received requires DLP / in-meeting chat DLP enablement, additional account-level enablement, or reviewer approval before this event will fire for a user-managed General app?