detektu
Supported APIs

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

Monitor Vercel freeDeprecation calendar

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.

  1. Potentially breaking
    Response property one of removed: payloadopenapi:GET /v3/events::response.200.application.json.events.items.payload
    Vercel API
  2. Info
    Response property became required: defaultDeploymentProtectionopenapi:PATCH /v2/teams/{}::response.200.application.json.body
    Vercel API
  3. Info
    Response property became required: defaultDeploymentProtectionopenapi:GET /v2/teams/{}::response.200.application.json.body
    Vercel API
  4. Info
    Response property became required: defaultDeploymentProtectionopenapi:GET /v2/teams::response.200.application.json.teams.items.oneOf[#.components.schemas.Team]
    Vercel API
  5. Info
    Response optional property added: githubUsageopenapi:POST /v11/projects::response.200.application.json.permissions.githubUsage
    Vercel API
  6. Info
    Response optional property added: connexClientAccessopenapi:POST /v11/projects::response.200.application.json.permissions.connexClientAccess
    Vercel API
  7. Info
    Response optional property added: githubUsageopenapi:GET /v10/projects::response.200.application.json.oneOf[subschema-#3].projects.items.permissions.githubUsage
    Vercel API
  8. Info
    Response optional property added: connexClientAccessopenapi:GET /v10/projects::response.200.application.json.oneOf[subschema-#3].projects.items.permissions.connexClientAccess
    Vercel API
  9. Info
    Response optional property added: githubUsageopenapi:PATCH /v1/projects/{}/microfrontends::response.200.application.json.permissions.githubUsage
    Vercel API
  10. Info
    Response optional property added: connexClientAccessopenapi:PATCH /v1/projects/{}/microfrontends::response.200.application.json.permissions.connexClientAccess
    Vercel API

Coverage

What Detektu monitors

Official products and contracts checked for changes.

Vercel API

  • OpenAPI contractOpenAPI contractStable

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.

Monitor Vercel free See pricing