[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-21-sandboxes-v1-endpoints-removed-v2-schema-changes-for":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KS5V4T27AYKGWX11BDTS28MM","2026-05-21-sandboxes-v1-endpoints-removed-v2-schema-changes-for","Breaking","Sandboxes v1 endpoints removed; v2 schema changes for Session\u002FSandbox","A large number of sandbox-related endpoints under `\u002Fv1\u002Fsandboxes` (and likely other `\u002Fv1\u002F` sandbox paths) have been **removed** from the spec — including `GET \u002Fv1\u002Fsandboxes` and `POST \u002Fv1\u002Fsandboxes` — which is a breaking change for any client using those endpoints. Simultaneously, several new schemas were added (`SandboxInjectionRule`, `SandboxNetworkPolicy`, `SandboxPublicRoute`, `Snapshot`) and the `status` enum ordering in the `Session` schema was reordered (values remain the same but `\"failed\"` and `\"aborted\"` moved positions). The net effect is that the v1 Sandboxes API surface is being dropped in favour of a v2 model.","2026-05-21T18:00:43.847Z"]