© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•5mo ago•
8 replies
Redcoat Trader

Exposing Schema

Hey everyone, I'm having a heck of a time with a schema I've created that SHOULD be exposed (see screenshot).

Steps I've taken:
- Enable & Save wait 30s, Disable & Save wait 30s, Enable & Save wait 30s
- Upgrade Postgres version to the latest
- Restarted the project (multiple times)
- Enabled RLS
- Applied ALL of the recommended Alter table/grant usage on schema, etc

I'm really at a loss on what to do at this point. I can't get a simple curl to work:
curl -s -H "apikey: $DEV_SUPABASE_SERVICE_ROLE" -H "Authorization: Bearer $DEV_SUPABASE_SERVICE_ROLE" -H "Accept-Profile: billing" "$SUPABASE_DEV_URL/rest/v1/billing.subscriptions"
{"code":"PGRST106","details":null,"hint":null,"message":"The schema must be one of the following: public, ref, mkt, analytics, ingest, cfg"}%

(and yes, I've validated those environment variables by doing the same thing with a different exposed schema, and I've tried it using Content-Profile with Accept-Profile, without Accept-Profile, and any other combination I can think of)
image.png
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

Similar Threads

Custom Schema and Exposing APIs
SupabaseSSupabase / help-and-questions
13mo ago
Exposing non-public schema to postgrest
SupabaseSSupabase / help-and-questions
13mo ago
Self hosted exposing schemas problems
SupabaseSSupabase / help-and-questions
2mo ago
Dynamically exposing custom schemas to API
SupabaseSSupabase / help-and-questions
3y ago