How to test OBF token implementation with external Zoom accounts if unpublished app can't be installed outside developer account?

API and Webhooks
1

Hi,

We’re implementing OBF (On Behalf Of) tokens for our Meeting SDK app following the March 2, 2026 requirement for apps joining meetings outside their own Zoom account.

Our implementation is complete:

  • Backend fetches the OBF token via GET /v2/users/{userId}/tokentype=onbehalf&meeting_id={meetingId}
  • Frontend passes the obfToken parameter to the Web SDK (@zoom/meetingsdk 4.1.0)

We’ve verified this works for meetings hosted within our own Zoom workspace. However, the whole point of the OBF token is to join meetings hosted on external Zoom accounts.

The problem: To test with an external account, we need a user from a different Zoom workspace to authorize our app (so we can get their OAuth access token and fetch the OBF token on their behalf). But when an external user tries to authorize our app, the OAuth flow fails — they’re redirected to App Marketplace with no specific error message.

From what I have read in other forum posts, this appears to be because dev apps cannot be installed outside the developer’s account.

Our question:

  • What is the recommended way to test OBF token functionality with external Zoom accounts during development? Specifically:
    1. Do we need to submit our app for Marketplace review before we can test the cross-account OBF flow?

Details:

  • App type: OAuth (Meeting SDK)
  • SDK version: @zoom/meetingsdk 4.1.0
  • Scope added: user:read:token (for OBF token endpoint)
  • OAuth flow works for users within our workspace
  • External user’s OAuth redirect results in App Marketplace (no error code in URL)

Thank you for any guidance.