Shopify just lifted a major ceiling on the data you can receive through Amazon EventBridge. The payload limit for both classic webhooks and Events has jumped from 256 KB to a full 1 MB (1,000,000 bytes). That sounds technical, but the impact is simple: larger product catalogs, orders with many line items, and rich resource objects now arrive inline, cutting down extra API calls and download steps. In this post we break down the change, who it affects, and the exact actions you should take to keep your apps running smoothly.
What Changed
Previously, EventBridge capped webhook payloads at 256 KB. Anything bigger fell back to a minimal JSON body like {"id":...} for classic webhooks, forcing a follow‑up Admin API request to pull the full resource. For Events, oversized payloads were replaced with a temporary payload_url that you had to download. Now Shopify sends raw UTF‑8 payloads up to 1 MB directly to your EventBridge partner event source, staying under EventBridge’s 1 MiB entry limit for the envelope. Only payloads that exceed 1 MB still use the old fallback mechanisms.
Who Is Affected?
The change is transparent for merchants—they won’t see a UI difference—but it’s a big win for developers who build apps that consume Shopify webhooks or Events via EventBridge. If your integration already subscribes to product, order, or inventory events, the larger payloads arrive automatically. No code changes are required to benefit from the increase, but you should review any custom fallback logic you’ve written for payloads over 256 KB.
How It Impacts Your Apps
What To Do – Actionable Steps
Even though Shopify applied the change automatically, a quick audit will keep your integration rock‑solid:
shopify.app.toml file or GraphQL eventBridgeWebhookSubscriptionCreate calls continue to work. No version bump is needed.{ "id": ... } shape (classic webhooks) or the payload_url stub (Events) for payloads that still exceed 1 MB. Example fallback snippet:js
if (event.detail.payload_url) {
// Download large payload
const resp = await fetch(event.detail.payload_url);
const data = await resp.json();
// process data
} else {
// Inline payload – use event.detail directly
const data = event.detail;
}
{
"inputPathsMap": { "detail": "$.detail" },
"template": "{ \"id\": <detail.id>, \"title\": <detail.title> }"
}
include_fields on the subscription query to request only the fields your app consumes. This reduces the chance of hitting the 1 MB ceiling.payload_url or a bare { "id": ... }. A sudden rise could indicate a new large resource type that needs special handling.Best Practices for Large EventBridge Payloads
id, title, price), request those fields explicitly. This keeps payloads small and speeds up downstream processing.Conclusion & Call to Action
The 1 MB payload boost for Amazon EventBridge is a quiet but powerful upgrade for Shopify developers. It removes a longstanding bottleneck, cuts extra API traffic, and lets you build richer, more responsive apps. Take a few minutes today to review your fallback logic, confirm your AWS target limits, and tighten your include_fields queries. Doing so will ensure you capture the full benefit of the new limit and keep your integrations fast and reliable.
Ready to future‑proof your Shopify app? Dive into your shopify.app.toml, run a quick log audit, and let the larger payloads work for you. If you need help adjusting your EventBridge rules or optimizing Lambda handlers, reach out to our developer community or consult the Shopify Dev docs.
