Supabase Management API
GET /v1/projects/{id}/analytics/endpoints/logs.all endpoint removal
Stopped workingSubscribe to Supabase Management APIShare
On September 23, 2026, the Supabase Management API endpoint GET /v1/projects/{id}/analytics/endpoints/logs.all was removed. Requests sent to this endpoint fail since that date. The change took effect two months after its announcement.
Calls it hits
GET /v1/projects/{id}/analytics/endpoints/logs.all
What to use instead of these calls
Call analytics/endpoints/logs instead, with ClickHouse SQL filtered by source_name.
In Supabase Management API's words
The logs.all Management API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement.
Facts
- API
- Supabase Management API
api.supabase.com - Kind
- Endpoint removal
- Announced
- July 23, 2026
- Takes effect
- September 23, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Supabase Management API's own pages
Questions
When does this change take effect?
Calls to GET /v1/projects/{id}/analytics/endpoints/logs.all on Supabase Management API stopped working on September 23, 2026.
What happens to calls after September 23, 2026?
They have failed since September 23, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Supabase Management API 1
-
No date
/v1/projects/{id}/api-keys/legacyEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.