// AI Platform Drift
Cloudflare Email API uses 'address' field in REST, 'email' in Workers
Cloudflare developer changelog · published 2026-11-17 20:59 UTC
WHAT CHANGEDThe REST API for Cloudflare Email now uses 'address' as the field name for recipient email addresses, while the Workers binding continues to use 'email'. Both accept an optional 'name' field for display names on to, cc, bcc, replyTo, and from.
WHY IT MATTERSCode calling the REST API directly with the 'email' field will fail or send incorrectly. Workers binding calls are unaffected, creating a divergence between the two interfaces to the same service.
WHAT TO DOIf you call the Cloudflare Email REST API, change recipient field names from 'email' to 'address'. Workers binding code requires no change.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
https://developers.cloudflare.com/changelog/post/2026-05-28-named-email-recipients/ Thu, 28 May 2026 00:00:00 GMT -You can now send emails with display names on recipient addresses in addition to the existing from support. Pass an object with email and an optional name field for to, cc, bcc, replyTo, or from: +You can now send emails with display names on recipient addresses in addition to the existing from support. With the Workers binding, pass an object with email and name fields for to, cc, bcc, replyTo, or from. With the REST API, the object uses address and an optional name: src/index.jsjsexport default { async fetch(request, env) { const response = await env.EMAIL.send({
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.85, needed 0.5 |
|---|---|
| triage reasoning | Breaking API change to REST endpoint field naming and structure for email recipients. |
| signals | API contract change: REST API now uses 'address' field instead of 'email' · binding-specific behavior documented: Workers binding vs REST API divergence · field requirement change: 'name' field behavior differs between implementations |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |