App Chatbot integration stopped working | Community
Skip to main content
D
New Member
Dalibor Grudenic
New Member
March 2, 2026
Question

App Chatbot integration stopped working

  • March 2, 2026
  • 1 reply
  • 22 views

Some of the customers using our Marketplace App started reporting an issue when using our zoom integration.

I’m not going to get in lot of details about our integration but basically the workflow is when you start the zoom meeting you get an chatbot message with 3 buttons you can press and depending which one you press different action gets triggered….

Around 10 days ago customers started reporting that nothing happens when they press button and on our side in the logs I can see 403 when calling API:

Failed to execute command: POST: api.zoom.us. Status code returned: 403 : response body was:

{"code":7004,"message":”Not authorized.","result":false}

We tried a lot of things but one thing that kind of uncloged everything and where we started seeing things getting back to normal was when we manually  execute bellow against customers account_id

curl -X POST https://api.zoom.us/v2/im/chat/messages \
-H "Authorization: Bearer xxx" \
-H "Content-Type: application/json" \
-d '{
"account_id": "xxx",
"content": { "head": { "text": "Connection Test" } },
"robot_jid": "xxx",
"to_jid": "xxx",
"user_jid": "xxx",
"is_markdown_support": true
}'

Any explanation/reasoning behind this?

1 reply

J
Newcomer
James Smite
Newcomer
March 2, 2026

This definitely looks like an authorization/state issue rather than a button or chatbot logic problem.

The {"code":7004,"message":"Not authorized."} response from the Zoom Video Communications API usually means one of the following:

Most Likely Causes

1️⃣ Token scope / permission changes
If you’re using a Server-to-Server OAuth app, Zoom may have:

  • Expired the token silently

  • Required re-consent for new scopes

  • Changed scope enforcement

Double-check:

  • The app still has chat_message:write (or relevant chat scopes)

  • The token is being refreshed properly

  • The account hasn’t revoked the app

2️⃣ Account-level authorization drift
Since manually sending a message with:

 

POST https://api.zoom.us/v2/im/chat/messages

“unclogged” things, that strongly suggests:

  • The bot wasn’t fully authorized at the account level

  • The chatbot connection was in a partially broken state

  • Or Zoom required a fresh interaction to revalidate permissions

In other words, your manual call likely re-established trust/state between:

  • account_id

  • robot_jid

  • user_jid

3️⃣ Marketplace app revalidation
If this is a Marketplace app, Zoom sometimes:

  • Forces reauthorization when scopes change

  • Requires reinstall after permission updates

  • Invalidates older tokens after backend changes

Have affected customers:

  • Remove the app

  • Reinstall it

  • Reauthorize fully

That often clears 7004 issues immediately.

Why It Started 10 Days Ago

When multiple customers suddenly see it:

  • It’s rarely their fault

  • Usually a backend enforcement change on Zoom’s side

  • Or stricter scope validation

Zoom has tightened Chatbot permissions before without obvious announcements.

What I’d Do Next

  1. Log the exact token type (S2S OAuth vs user-level OAuth).

  2. Verify scopes against current Zoom Marketplace configuration.

  3. Add logging for:

    • Token expiration

    • Account ID mismatch

    • JID mismatch

  4. Ask one affected customer to:

    • Fully uninstall

    • Reinstall

    • Reauthorize

Key Signal

The fact that your manual im/chat/messages call fixes it temporarily strongly suggests:

  • Authorization state desync

  • Not a broken integration logic issue

If you want, tell me:

  • Are you using Server-to-Server OAuth?

  • Is this a Chatbot app type?

  • Did you change scopes recently?

That’ll narrow it down fast.

Terms & ConditionsAccessibility statement
Copyright © Zoom Communications, Inc. All rights reserved.