What Supabase Management changed, 23 April 2026 to 26 October 2026
161 operations became 170. None were removed, 1 were newly deprecated, 9 were added, and 0 request fields became required.
Read from supabase/supabase at 7f638a8 and ce393db (version 1.0.0). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Supabase Management's published specification.
Supabase keeps the description of its Management API (api.supabase.com/v1) in supabase/supabase, at apps/docs/spec/api_v1_openapi.json. This page reads that file; it does not cover the per-project database, auth or storage APIs. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
- GET /v1/projects/{ref}/analytics/endpoints/logs.all deprecated in eb21ae2 · 29 June 2026
Deprecated as of the current specification (2)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
- GET /v1/projects/{ref}/analytics/endpoints/logs.all
- POST /v1/projects/{ref}/functions
Entries without a link were already marked deprecated at 7f638a8 · 23 April 2026, the baseline compared here.
Supabase Management API questions
Every answer below is computed from the snapshot above, and each links to the Supabase Management specification it was read from.
- Which Supabase Management API endpoints were removed recently?
- None between 23 April 2026 and 26 October 2026, in apps/docs/spec/api_v1_openapi.json in supabase/supabase. It went from 161 to 170 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: supabase/supabase, the two commits compared
- Which Supabase Management API endpoints are deprecated?
- As of 26 October 2026, apps/docs/spec/api_v1_openapi.json in supabase/supabase marks 2 operations deprecated: GET /v1/projects/{ref}/analytics/endpoints/logs.all and POST /v1/projects/{ref}/functions. 1 compared operation (paired with a baseline operation) gained the deprecated flag between 23 April 2026 and 26 October 2026. 1 was already deprecated at the baseline.
- Source: supabase/supabase, the two commits compared
- Did any Supabase Management API request fields become required?
- None between 23 April 2026 and 26 October 2026, among the JSON request bodies in apps/docs/spec/api_v1_openapi.json in supabase/supabase the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: supabase/supabase, the two commits compared
- Where is the Supabase Management OpenAPI specification?
- In the supabase/supabase repository on GitHub. This page reads apps/docs/spec/api_v1_openapi.json at commit ce393db (version 1.0.0), dated 26 October 2026.
- Source: supabase/supabase on GitHub
The Action does not check Supabase Management yet
It checks GitHub REST and Stripe. If you want your CI to check the Supabase Management endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.