cd /news/ai-infrastructure/breaking-cloudflare-response-field-r… · home › topics › ai-infrastructure › article
[ARTICLE · art-158618] src=driftwatch.et ↗ pub= topic=ai-infrastructure verified=true sentiment=↓ negative

Cloudflare: Response field result removed

Cloudflare removed the result field from responses to GET /accounts/{account_id}/ai-gateway/gateways, so reads of that field now return undefined and fail wherever the value is used rather than at the call site. The change, reported against Cloudflare's published API specification, breaks code that assigns response.result directly, such as `const result = response.result;`.

read1 min views2 publishedOct 27, 2026

What changed #

Reads of this field return undefined, and the failure surfaces wherever that value is used rather than at the call.

Affects GET /accounts/{account_id}/ai-gateway/gateways.

Who is affected #

Code that reads GET /accounts/{account_id}/ai-gateway/gateways (result).

Before and after #

Where Before After
GET /accounts/{account_id}/ai-gateway/gateways · result present absent

Code that breaks #

// response.result is now undefined
const result = response.result;

Based on Cloudflare’s published API specification. How severity is decided.

── more in #ai-infrastructure 4 stories · sorted by recency
── more on @cloudflare 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/breaking-cloudflare-…] indexed:0 read:1min 2026-10-27 · —