[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-07-13-new-required-field-tokenid-added-to-a-response-object":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},"01KXEVC1AWR8JEJCCY89V5GVX9","2026-07-13-new-required-field-tokenid-added-to-a-response-object","Breaking","New required field `tokenId` added to a response object","A new field **`tokenId`** (type `string`) has been added to a response object's `properties` and simultaneously added to its `required` array alongside the existing `token`, `connector`, and `expiresAt` fields. Because `tokenId` is marked **required** in the schema, any client that validates responses against this spec will now fail if the server doesn't return it — and any server implementation that doesn't yet emit it will produce invalid responses. This is a breaking schema change for strict consumers.","2026-07-13T23:00:37.852Z"]