Hi everyone,
I’m currently preparing a Zoom OAuth Marketplace app for an event management platform called Ticket Deck (ticket-deck.com), and I’m running into an issue with domain verification.
The app uses:
-
Zoom OAuth user-level app
-
Supabase Edge Functions for OAuth handling
-
React/Vite frontend hosted through Lovable
-
HTTPS/TLS enabled
I’m trying to verify the domain using the HTML file method.
Zoom generated this file:
ZOOM_verify_b8d30634336f4b9588c7aae58a972085.html
The file has been added to the root/public directory and is accessible at:
https://ticket-deck.com/ZOOM_verify_b8d30634336f4b9588c7aae58a972085.html
When visiting the URL directly in the browser, it correctly displays only:
b8d30634336f4b9588c7aae58a972085
The app has also been republished/deployed after adding the file.
However, Zoom still returns:
“Domain verification failed.”
A few things I’d like to confirm:
-
Does Zoom cache failed verification attempts for some time?
-
Does the verification file need any specific content-type/header?
-
Can Cloudflare/Lovable hosting affect Zoom’s verification crawler?
-
Does the file need to be served outside SPA routing in a special way even if the URL opens correctly?
-
Is there anything else Zoom checks besides accessibility + exact content?
Would appreciate any guidance from anyone who has dealt with this before.
Thanks!