Supabase APIBreaking changecritical
Supabase removes the Management API logs.all endpoint on Sep 23, 2026
- Detected
- Oct 12, 2026
- Confidence
- 97%
What changed
This diff contains numerous breaking changes, deprecations, and new features across Supabase's platform. The most critical breaking changes include: removal of the Management API logs.all endpoint (2026-09-23), PostgreSQL 15.19/17.11 upgrade requiring reindexing and re-encryption, Realtime schema lockdown, self-hosted API gateway switch from Kong to Envoy, OAuth token endpoint changing from HTTP 201 to 200, and several schema/auth/storage access restrictions.
What to do
Audit all of the following immediately: (1) Migrate scripts from logs.all to the new ClickHouse-backed logs endpoint before 2026-09-23; (2) Reindex ltree/btree_gist and re-encrypt pgcrypto data after Postgres 15.19/17.11 upgrade; (3) Update OAuth token checks from status 201 to any 2XX; (4) Migrate framework adapters out of @supabase/server before 2026-12-01; (5) Upgrade Node.js to 22+ before 2026-06-30; (6) Replace account-level PATs with scoped tokens; (7) Self-hosted users must reconfigure for Envoy gateway and new API_EXTERNAL_URL format.
Affected
endpoint: GET /projects/{ref}/analytics/endpoints/logs.allendpoint: /v1/oauth/tokenendpoint: /auth/v1/sso/saml/*endpoint: Management API /v1 and /v2 endpointsmodel: realtime schemamodel: auth schemamodel: storage schemamodel: pgmq delay parametermodel: pg_graphql introspectionmodel: @supabase/server framework adapters (Hono, H3, Elysia, NestJS)param: CREATE EXTENSION version clauseparam: API_EXTERNAL_URLheader: SUPABASE_ACCESS_TOKENSource: supabase.com (Supabase's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Supabase SDK and the names above:
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