App Submission URL verify problem

API and Webhooks
1

Description

I’m integrating the Zoom API to allow users to browse and download Zoom Cloud recordings from other authorized Zoom accounts (with appropriate scopes such as recording:read). The application works as expected in our staging environment.

However, during the App Marketplace submission process, I encountered an issue in the “Verify Domains” step. Only one domain (example.com) appears in the “Verify Domains” list, and I have already successfully verified it (status: VERIFIED).

Yet when I attempt to submit the app, I receive the following error message:

“All domains must be verified.”

I double-checked all relevant fields (OAuth allow list, Privacy Policy URL, Documentation URL, etc.), and although I am using subdomains (e.g., staging.example.com, www.example.com), these do not appear in the domain verification list, so I have no way to verify them directly in the UI.

How To Reproduce

  1. App Type: OAuth App for Zoom Marketplace
  2. Relevant domain-related configuration:
  • Home URL: https://staging.example.com/
  • Privacy Policy URL: https://www.example.com/privacy-policy/
  • Terms of Use URL: https://www.example.com/terms-of-service/
  • Support URL: https://www.example.com/contact-us/
  • OAuth Allow List includes:
    • https://staging.example.com/
    • https://localhost:8443/
  1. Verified Domain:
  • example.com (status: VERIFIED)
  1. Error on Submit:

“All domains must be verified.”

Request for Support

  • Why are subdomains like staging.example.com or www.example.com not showing up in the domain verification list, even though they are clearly being used in the app config?
  • How can I verify these domains if they are not explicitly listed?
  • Is this expected behavior, and is there a workaround to proceed with submission?

Thanks in advance for your help!
Bin Yang
:e_mail:bin.yang@civi.com

2

hi @Brian12 ,
You can not have a local host for oAUth.
Zoom can not find a local domain when it returns the values.

2nd, it looks like you are using staging.example.com which I assume is your dev install.
You must have a second build for your live install.
Otherwise you will never be able to reuest an upgrade of a new version becuase the live version must be locked and only the dev one change.
hope that makes sense
all the best

John

1 Like
3

Thank you so much John, I delete the local host and fix that problem.
It works~

4

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.