Cloudflare API
- OpenAPI contract
Vendor coverage
Cloudflare API changes & breaking changes
Cloudflare iterates across dozens of products behind one API, and its published OpenAPI schemas change constantly. Detektu diffs every revision and scopes the noise down to the endpoints you depend on.
Last checked Oct 20, 2026, 4:44 PMLast change detected Oct 20, 2026, 4:45 PM
Detected changes
Latest Cloudflare API changes
Every entry is a change Detektu detected in Cloudflare's published contracts, with exact before/after evidence on its page.
- Potentially breakingResponse required property removed: logpushJob
openapi:DELETE /accounts/{}/workers/observability/destinations/{}::response.200.application.json.result.configuration.logpushJob - Potentially breakingResponse required property removed: destination_conf
openapi:DELETE /accounts/{}/workers/observability/destinations/{}::response.200.application.json.result.configuration.destination_conf - Potentially breakingResponse required property removed: logpushJob
openapi:POST /accounts/{}/workers/observability/destinations::response.201.application.json.result.configuration.logpushJob - Potentially breakingResponse required property removed: destination_conf
openapi:POST /accounts/{}/workers/observability/destinations::response.201.application.json.result.configuration.destination_conf - Potentially breakingResponse required property removed: destination_conf
openapi:GET /accounts/{}/workers/observability/destinations::response.200.application.json.result.items.configuration.destination_conf - BreakingResponse property became nullable
openapi:GET /accounts/{}/workers/observability/destinations::response.200.application.json.result.items.configuration.headers.additionalProperties. - InfoRevertedApi version not bumped
openapi:* *::operation.api-version-not-bumped - InfoResponse required property added: is_used_in_update
openapi:GET /accounts/{}/one/applications/{}/setup-flows::response.200.application.json.result.items.steps.items.is_used_in_update - InfoResponse required property added: is_used_in_create
openapi:GET /accounts/{}/one/applications/{}/setup-flows::response.200.application.json.result.items.steps.items.is_used_in_create - InfoResponse required property added: is_used_in_update
openapi:GET /accounts/{}/one/applications/{}/setup-flows::response.200.application.json.result.items.steps.items.form_fields.items.is_used_in_update
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Cloudflare ships changes
The release patterns that shape your integration risk.
Cloudflare publishes machine-readable API schemas covering its whole surface: DNS, Workers, R2, Zero Trust, and everything in between. The pace of change is high, with new endpoints, extended request bodies, and tightened responses. Almost none of it matters to any single customer, which is exactly why diff noise is the problem.
Detektu detects every structural change but correlates findings with your declared usage, so a schema change in a product you don't touch stays informational while a change under an endpoint you call is escalated.
Monitored for you
Do Cloudflare's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Cloudflare findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.