Skip to main content
Fullstack apps include a dedicated managed Postgres database. These endpoints run against it via the backend management API — Naive injects the credentials.

List Tables

Lists tables in the public schema. row_count is PostgreSQL’s planner estimate (pg_class.reltuples) — fast, but approximate until the table has been analyzed.

Run Query

Request Body

Response

Returns the result rows as a JSON array (empty array for statements that return no rows):
200
Only available for apps created with type: fullstackfrontend_only apps return 501 feature_not_configured. Queries run with full admin privileges (no RLS), so treat this as a root database console.

Going Further

  • Tracked migrations, auth config, storage, edge functions — use the Backend proxy, which exposes the entire backend management API scoped to this app’s project.
  • Row-level data access via PostgREST — use ANY /v1/apps/:id/db/rest/* (documented on the Backend proxy page).
  • From your app code — use @supabase/supabase-js with the auto-injected NEXT_PUBLIC_SUPABASE_URL / NEXT_PUBLIC_SUPABASE_ANON_KEY.

Errors

501
502