Supabase APIBreaking changehigh

Supabase swaps logs.all for ClickHouse logs endpoint on Sep 23, 2026

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

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 that uses a different SQL dialect, a unified table structure, 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 queries to ClickHouse SQL, filter by source_name in a WHERE clause instead of selecting per-source 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_attributes

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 →