Driftwatch

Vercel / Vercel REST API /

Breaking

Response field createdAt removed

What changed

Reads of this field return undefined, and the failure surfaces wherever that value is used rather than at the call.

Affects GET /v1/global-config.

Who is affected

Code that reads GET /v1/global-config (createdAt).

Before and after

WhereBeforeAfter
GET /v1/global-config · createdAtpresentabsent
GET /v1/global-config · createdBypresentabsent
GET /v1/global-config · deletedAtpresentabsent
GET /v1/global-config · digestpresentabsent
GET /v1/global-config · idpresentabsent
GET /v1/global-config · itemCountpresentabsent
GET /v1/global-config · ownerIdpresentabsent
GET /v1/global-config · purposepresentabsent
GET /v1/global-config · schemapresentabsent
GET /v1/global-config · sizeInBytespresentabsent
GET /v1/global-config · slugpresentabsent
GET /v1/global-config · syncedToDynamoAtpresentabsent
GET /v1/global-config · transferpresentabsent
GET /v1/global-config · updatedAtpresentabsent

Code that breaks

// response.createdAt is now undefined
const createdAt = response.createdAt;

Based on Vercel’s published API specification. How severity is decided.