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.
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.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Older deployments endpoint version deprecated
openapi:GET /v6/deploymentsNew field on project response
openapi:GET /v9/projects/{idOrName} ::response.200.rollingReleaseMonitored 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.