# Requesting a manual domain bypass for supabase.co

**URL:** <https://devforum.zoom.us/t/requesting-a-manual-domain-bypass-for-supabase-co/144837>\
**Category:** Authentication\
**Created:** [July 17, 2026, 6:15pm UTC](https://devforum.zoom.us/t/requesting-a-manual-domain-bypass-for-supabase-co/144837 "2026-07-17T18:15:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Linda6](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/linda6/32/75518_2.png) [@Linda6](https://devforum.zoom.us/u/Linda6)\
**Post date:** [July 17, 2026, 6:15pm UTC](https://devforum.zoom.us/t/requesting-a-manual-domain-bypass-for-supabase-co/144837/1 "2026-07-17T18:15:51Z")

</div>

Hello Zoom Marketplace Team,

I am requesting manual domain verification or bypass for a Supabase OAuth callback URL used by our production Zoom OAuth app.

Our primary application domain is verified:  
globalcfoclientportal[dot]com

Our app uses Supabase Auth as backend authentication infrastructure. Supabase is a managed Platform-as-a-Service provider, so the OAuth callback is hosted on our Supabase project domain:

xyxnbwheuokpkkoaepoj[dot]supabase[dot]co/auth/v1/callback

We do not own the parent domain supabase[dot]co, so we cannot verify it through DNS, HTML file upload, or meta tag verification. This callback is used only for the secure OAuth redirect handled by Supabase Auth. End users interact with our application at globalcfoclientportal[dot]com.

Zoom App Name: global cfo client portal  
Client ID: faQNuWGFTgOih9SovML5Ww  
Verified primary domain: globalcfoclientportal[dot]com

Please manually approve or bypass domain verification for this Supabase callback URL.
