← All breaking-change reports

Cloudflare API breaking change: operation-removed on DELETE /accounts/{account_id}/cloudforce-one/events/{event_id}

cloudflare · breaking · 2026-03-31 · source: OpenAPI spec diff

What changed

According to the OpenAPI spec diff (cloudflare/cloudflare-oas-b61f904f10c9-to-7abe88500e55-removals), the following surface changed:

operation-removed: DELETE /accounts/{account_id}/cloudforce-one/events/{event_id}

cloudflare OAS corridor pair b61f904f10c9 -> 7abe88500e55 (removals subset ingested 2026-08-01)

Who is affected

Delete or gate every call site that issues DELETE against cloudforce-one events: the verb now returns method-not-allowed.

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:

Delete or gate every call site that issues DELETE against cloudforce-one events: the verb now returns method-not-allowed. Removing the delete invocation (and any UI affordance wired to it) is the mechanical mend; if soft-deletion semantics are needed, PATCHing the event into an archived state is the surviving write surface, but adopting that policy is a product decision outside the codemod.

Before:

await cf.delete(`/accounts/${acct}/cloudforce-one/events/${eventId}`);

After:

// DELETE on cloudforce-one events was withdrawn upstream; call removed.
// The event remains readable via GET and editable via PATCH on the same path.

Replacement data source: the same event resource remains readable and editable via the surviving GET and PATCH operations on the identical path

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.