Vercel API
- OpenAPI contract
Vendor coverage
Vercel API changes & breaking changes
Vercel's REST API versions endpoints individually: deployments, projects, and domains each move on their own schedule. Detektu diffs the published spec so your deployment automation doesn't lag behind an endpoint bump.
Last checked Oct 20, 2026, 7:06 PMLast change detected Oct 20, 2026, 7:06 PM
Detected changes
Latest Vercel API changes
Every entry is a change Detektu detected in Vercel's published contracts, with exact before/after evidence on its page.
- InfoRevertedApi version not bumped
openapi:* *::operation.api-version-not-bumped - InfoResponse body one of removed: subschema-#3
openapi:POST /v2/sandboxes/sessions/{}/cmd::response.200.subschema-#3 - InfoResponse optional property added: refundedTotal
openapi:GET /v1/installations/{}/billing/invoices/{}::response.200.application.json.refundedTotal - InfoResponse optional property added: pendingRefundTotal
openapi:GET /v1/installations/{}/billing/invoices/{}::response.200.application.json.pendingRefundTotal - InfoResponse optional property added: paidTotal
openapi:GET /v1/installations/{}/billing/invoices/{}::response.200.application.json.paidTotal - InfoResponse optional property added: outstandingTotal
openapi:GET /v1/installations/{}/billing/invoices/{}::response.200.application.json.outstandingTotal - Potentially breakingRequest parameter removed: cmdId
openapi:POST /v2/sandboxes/sessions/{}/cmd::query.cmdId - BreakingResponse property one of added: data
openapi:GET /v3/events::response.200.application.json.events.items.payload.oneOf[subschema-#80].data - InfoRevertedApi version not bumped
openapi:* *::operation.api-version-not-bumped - Potentially breakingResponse property one of removed: payload
openapi:GET /v3/events::response.200.application.json.events.items.payload
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Vercel ships changes
The release patterns that shape your integration risk.
Per-endpoint versioning means there is no single 'API version' to track: /v13/deployments and /v9/projects evolve independently, and older endpoint versions are deprecated individually. That granularity is easy to automate against and hard to audit by hand.
Detektu treats each operation as its own coordinate, so a new deployment endpoint version or a deprecated project route is reported exactly where it happened, matched against the operations your CI actually calls.
Monitored for you
Do Vercel's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Vercel findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.