© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•5w ago•
73 replies
Dirt

400 Validation Error on Twitter OAuth (Provider Enabled)

auth
Using Bolt.new to build my webapp. Claimed supabase database.

Supabase: Twitter provider is toggled ON.

Twitter Dev Portal: App is set to "Web App," User Authentication is ON, and "Request email from users" is enabled.

Callback URL: Copied directly from Supabase into Twitter Dev settings.

Env Vars: Cannot confirm that the SUPABASE_URL and ANON_KEY match the project where the provider is enabled because Bolt automatically created the new supabase org when I clicked it.

The Issue: Despite everything being "ON," the API response still claims the provider is disabled. Is there a known delay in provider propagation, or a specific "Site URL" wildcard setting in Supabase Auth that I might be missing for Bolt.new preview URLs?

Appreciate any insights!
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements
Next page

Similar Threads

Google Auth Enabled, but getting 'provider is not enabled' 400 Error
SupabaseSSupabase / help-and-questions
4y ago
How to check if given OAuth provider is enabled?
SupabaseSSupabase / help-and-questions
13mo ago
X/Twitter OAuth confusion
SupabaseSSupabase / help-and-questions
5mo ago
Google oauth error 400: redirect uri mismatch
SupabaseSSupabase / help-and-questions
14mo ago