Supabase APIBreaking changehigh
Supabase removes the logs.all analytics endpoint on Sep 23, 2026
- Detected
- Aug 20, 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 September 23, 2026, replaced by a new ClickHouse-backed logs endpoint with a unified table, different SQL dialect requirements, and a flat log_attributes map instead of nested metadata arrays.
What to do
Update endpoint path from analytics/endpoints/logs.all to analytics/endpoints/logs, convert SQL to ClickHouse dialect, filter by source_name in WHERE clause instead of selecting source-specific tables, and replace CROSS JOIN unnest(metadata) patterns with log_attributes['key'] map access.
Affected
endpoint: /analytics/endpoints/logs.allendpoint: /analytics/endpoints/logsparam: source_namemodel: log_attributesSource: 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