WhatsApp Cloud API: template images sent by old Meta CDN links fail with 400 Invalid Handle
What changed
In a September 14, 2026 change to its official WhatsApp sample app (fbsamples/whatsapp-business-jaspers-market, commit 8f45b6f), Meta wrote that the Cloud API rewrites old Meta CDN links to an internal origin that returns 400 Invalid Handle, so template sends are accepted but fail asynchronously. Meta switched the sample to images uploaded as media IDs. The sample's README says media IDs are scoped to the phone number that uploaded them and expire after 30 days. This is Meta's own finding in sample code, not a formal changelog announcement.
What it means
Template messages that point to an image by an old Meta CDN link can be accepted by the API and then fail, so the customer never gets the message.
Who is affected
Tools and businesses that send WhatsApp template messages with images, buttons or carousels by URL through the Cloud API.
What to do
Upload each image through the Cloud API media endpoint for your sending number and send it by media ID. Re-upload before 30 days, when media IDs expire.
What this means for you
If your WhatsApp messages include a picture, how the picture is attached matters. Pointing to an old Meta image link can make the message fail after it looks sent, so your customer sees nothing. Uploading the picture first and sending it by its upload number works. Those upload numbers last 30 days, so pictures have to be uploaded again each month.
The details
- Source: Meta's official sample app
fbsamples/whatsapp-business-jaspers-market, commit8f45b6f(September 14, 2026). The commit message: "Cloud API rewrites the old Meta CDN links to an internal origin that returns400 Invalid Handle, so three button flows are accepted but fail asynchronously." - Meta's fix in the sample: send template images with
image.id(a media ID from the Cloud API media endpoint) instead of a link. The app now refuses to start if a media ID is missing. - Media ID rules (README, lines 83 to 87): example handles are only for creating templates; runtime sends need media IDs uploaded for the phone number that sends; media IDs "are scoped to the phone number that uploaded them and expire after 30 days."
- Not stated: which CDN link formats are affected, when the rewrite started, or whether Meta announced it elsewhere. This entry rests on Meta's sample code, not a changelog, and this site does not read Meta's developer pages.
- More: WhatsApp Cloud API basics covers templates and media IDs.
What to do next
- Business owners: If template messages with pictures stopped arriving, ask your provider whether they send images by media ID.
- Marketers and agencies: Test one templated campaign with an image to a test number before a big send, and watch delivery status, not just "sent".
- Developers: Upload media per sending number, store the media IDs, rotate them before 30 days, and watch the message status webhooks for failures after a 200 response.
Primary sources
- Meta on GitHub: Send Jasper template media by uploaded ID (commit 8f45b6f, September 14, 2026)
- Jasper's Market README (media IDs: scope and 30-day expiry, lines 83 to 87)
Get an email when a new API change is added
Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.