Supabase APIBreaking changehigh
Supabase removes the logs.all analytics endpoint on Sep 23, 2026
- Detected
- Aug 21, 2026
- Effective
- Sep 23, 2026(took effect 54 days ago)
- Confidence
- 92%
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. Additionally, multiple other breaking changes are included in this diff spanning API endpoints, self-hosted gateway changes, schema lockdowns, and more.
What to do
Migrate all scripts calling the logs.all endpoint to the new logs endpoint using ClickHouse SQL before 2026-09-23. Also review other breaking changes: update OAuth token checks from 201 to 2XX, migrate self-hosted API gateway from Kong to Envoy, update API_EXTERNAL_URL to include /auth/v1, and stop relying on auto-exposed public schema tables.
Affected
endpoint: GET /projects/{ref}/analytics/endpoints/logs.allendpoint: GET /projects/{ref}/analytics/endpoints/logsendpoint: /v1/oauth/tokenendpoint: GET /projects/{ref}/analytics/endpoints/logs.all (Management API)param: API_EXTERNAL_URLmodel: realtime schemamodel: pg_graphql introspectionheader: x-deno-versionSource: 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