Supabase APIBreaking changecritical

Supabase removes the logs.all Management API endpoint on Sep 23, 2026

Detected
Aug 24, 2026
Effective
Sep 23, 2026(took effect 54 days ago)
Confidence
97%

What changed

The Supabase Management API logs.all analytics endpoint is being removed on 2026-09-23 and must be replaced with the new ClickHouse-backed logs endpoint, which only accepts ClickHouse SQL. Multiple other breaking changes are also present including Envoy replacing Kong as default API gateway, realtime schema lockdown, OAuth token endpoint returning HTTP 200 instead of 201, and several self-hosted configuration changes.

What to do

Migrate scripts from logs.all to the new logs endpoint using ClickHouse SQL before 2026-09-23. Additionally: update OAuth token checks from status 201 to any 2XX; if self-hosted, prepare for Envoy replacing Kong (week of 2026-08-09) and opt back into Kong if needed; note that extension version pinning in CREATE/ALTER EXTENSION is ignored from 2026-08-05; and review all other breaking changes for their respective effective dates.

Affected

endpoint: logs.allendpoint: /v1/oauth/tokenendpoint: GET /projects/{ref}/analytics/endpoints/logs.allmodel: realtime schemaparam: API_EXTERNAL_URLmodel: pg_graphqlmodel: Kong API gatewayparam: CREATE EXTENSION version clause

Source: supabase.com (Supabase's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the Supabase SDK and the names above:

npm: @supabase/supabase-jspip: supabaseruby: supabasego: github.com/supabase-community/supabase-gorust: postgrest

Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free

Get Supabase API changes by email

Once a week: the breaking changes and upcoming deadlines for Supabase, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Supabase API changes

Every Supabase API change →