Since last Friday 2026-04-10 around 14:00 UTC, at least checkouts/update webhooks have been intermittently arriving with the wrong API version payload.
This is still ongoing.
Our subscriptions are for 2025-07, which the received headers also confirm, but sometimes the payload is missing the id field, which is removed in 2026-04. Sometimes the field is present, so this doesn’t happen all the time.
Hi all, you’re correct that the id field should still be present for subscriptions on API versions older than 2026-04. This is a known platform-side issue, not something in your app’s configuration.
The behavior is store-specific because of how webhook payloads are formed internally. If a store happens to have another subscription for the same topic that resolves to 2026-04, the id removal applies to all subscriptions on that store, regardless of the version they’re actually pinned to. That’s why some stores are affected and others aren’t, even with an identical app setup.
Our engineering team has identified the root cause and a fix is being deployed. You don’t need to make any changes on your end. The id field will return to your payloads once the rollout completes.
We’re tracking this internally and will update this thread when the fix is fully rolled out. Thanks for flagging this with us!
What is the timeline of the fix? This is causing a pretty critical issue for our customers and need to communicate a timeline for them. Let us know, thanks.
Hi @fox, a fix has been deployed and is rolling out now. It started yesterday and already covers the majority of stores, so you should start seeing correct payloads soon if you haven’t already.
I don’t have an exact ETA on completion, but the rollout has been progressing steadily and should reach full coverage in the near term. If you’re still seeing the issue on specific stores and need it looked at sooner, feel free to reach out to Support via https://help.shopify.com/en → Chat WIth A Human with the affected shop domains and we can follow up with the team.