cd /news/ai-products/breaking-openai-type-is-no-longer-ac… · home › topics › ai-products › article
[ARTICLE · art-155652] src=driftwatch.et ↗ pub= topic=ai-products verified=true sentiment=· neutral

OpenAI: type is no longer accepted

OpenAI has removed the `type` field from `DecisionInputMessage`, affecting one OpenAI API operation, according to the company's published API specification. Calls that still send `type` will succeed rather than fail, because the field is now ignored instead of rejected, so code may silently behave differently. The change breaks code that relies on `type` being present on `DecisionInputMessage` objects.

read1 min views1 publishedOct 22, 2026

What changed #

Usually ignored rather than rejected, so the call succeeds and does something subtly different.

Affects type on DecisionInputMessage reachable from 1 operation. Grep for it: nothing else will tell you.

Who is affected #

Code that sends OpenAI's DecisionInputMessage objects, used by 1 OpenAI operation.

Before and after #

Where Before After
DecisionInputMessage.type present absent

Code that breaks #

await client.post("/…", {
  // type is now ignored, not rejected
  type: value,
});

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

── more in #ai-products 4 stories · sorted by recency
── more on @openai 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-openai-type…] indexed:0 read:1min 2026-10-22 · —