[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-07-17-get-image-endpoint-path-param-renamed-from-imageid-to":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},"01KXR9G7W7NQ8HF64DK5NTA301","2026-07-17-get-image-endpoint-path-param-renamed-from-imageid-to","Breaking","GET image endpoint path param renamed from imageId to imageIdOrDigest","The `GET \u002Fv1\u002Fvcr\u002Frepository\u002F{idOrName}\u002Fimages\u002F{imageId}` endpoint has been split: the **GET** operation now lives at `\u002Fv1\u002Fvcr\u002Frepository\u002F{idOrName}\u002Fimages\u002F{imageIdOrDigest}` with the path parameter renamed from `imageId` to `imageIdOrDigest`, while the **DELETE** operation remains at the original `{imageId}` path. Any client constructing the GET URL with the old path template `{imageId}` will now hit a non-existent route, and the parameter name change may break SDK\u002Fcode that references the parameter by name. The description update also documents that the new parameter accepts either an internal id (`image_...`) or a manifest digest (`sha256:...`).","2026-07-17T15:00:45.575Z"]