← All breaking-change reports

Vercel API breaking change: path-removed on /v1/edge-config/{edgeConfigId}/token

vercel · breaking · 2026-07-31 · source: OpenAPI spec diff

What changed

According to the OpenAPI spec diff (vercel/vercel-oas-v1.28.13-to-v1.28.14-removals), the following surface changed:

path-removed: /v1/edge-config/{edgeConfigId}/token

vercel OAS corridor pair v1.28.13 -> v1.28.14 (removals subset ingested 2026-08-01)

Who is affected

Mechanical path rewrite at every call site: replace the '/edge-config' segment with '/global-config' in raw URL builders, route constants, and API client wrappers hitting '/v1/edge-config/{edgeConfigId}/token'.

To find out whether your repo is hit — file and line number, no code leaving your machine:

npx mendapi scan --repo .

How to fix it

Migration path:

Mechanical path rewrite at every call site: replace the '/edge-config' segment with '/global-config' in raw URL builders, route constants, and API client wrappers hitting '/v1/edge-config/{edgeConfigId}/token'. The successor route exposes the same method set (post) with the same path parameters, so no request or response handling edits are required beyond the one-segment rename.

Before:

const res = await fetch(`https://api.vercel.com/v1/edge-config/${id}/token`, opts);

After:

const res = await fetch(`https://api.vercel.com/v1/global-config/${id}/token`, opts);

Replacement data source: the same resource is served at /v1/global-config/{edgeConfigId}/token in the NEW spec with an identical method set

With your own LLM key configured (BYO compute — mendapi never proxies your credentials), npx mendapi llmfix turns this guide into a reviewable draft patch for your repo.

Detected and tracked by mendapi — Dependabot for every API you depend on. Scans run locally; your code never leaves your machine.

Related

Change data is recorded from upstream provider releases, changelogs and OpenAPI spec diffs; every article names its source.