[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-26-sandboxes-api-paths-changed-from-v2-sandboxes-to-sandboxes":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},"01KSJCWP3TFGCR44G4VY1JTEAG","2026-05-26-sandboxes-api-paths-changed-from-v2-sandboxes-to-sandboxes","Breaking","Sandboxes API paths changed from \u002Fv2\u002Fsandboxes to \u002Fsandboxes, auth removed","All sandbox-related endpoints have been moved from `\u002Fv2\u002Fsandboxes\u002F*` to `\u002Fsandboxes\u002F*`, which is a breaking path change for any client hardcoding the versioned prefix. Additionally, `security` definitions (bearer token auth) and `tags` have been stripped from all sandbox operations, and `operationId` values have been renamed (e.g. `listSandboxes` → `getSandboxes`, `readSessionFile` → `createSandboxesSessionsBySessionIdFsRead`). The `teamId` and `slug` query parameters have also been removed from all sandbox endpoints, breaking any team-scoped requests. A new `429` (rate limit) response code has been added across many endpoints.","2026-05-26T15:01:45.210Z"]