You can now receive webhook and Events payloads up to 1 MB (1,000,000 bytes) through Amazon EventBridge, up from 256 KB. This increase applies automatically across all API versions, and you don't need to update your existing subscriptions.
What changed
Previously, Amazon EventBridge deliveries capped payloads at 256 KB:
- Classic webhook payloads over 256 KB fell back to a minimal
{"id": ...}body, requiring a follow-up Admin API request to fetch the full resource. - Events payloads over 256 KB used large-payload overflow and delivered a temporary
download link instead of the inline payload.
Shopify now sends raw UTF-8 payloads up to 1,000,000 bytes directly to your Amazon EventBridge partner event source, leaving headroom under EventBridge's 1 MiB entry cap for the source, detail-type, and detail envelope. Large resources such as products with many variants or orders with many line items now arrive inline, reducing follow-up Admin API requests and downloads in your app.
Payloads over 1,000,000 bytes keep the existing fallback behavior: classic webhooks send {"id": ...}, and Events deliveries send a stub payload with , , and .
What to do
No action is required. Existing EventBridge subscriptions configured in shopify.app.toml or through the GraphQL Admin API ( and ) automatically receive inline payloads up to 1 MB across all API versions.
To review how your app handles large deliveries:
- Keep fallback handling in place for payloads that exceed 1 MB (
{"id": ...}for classic webhooks andfor Events), or narrow payloads withand targeted Events[events.subscription]queryselections. - Verify that the downstream AWS targets attached to your EventBridge rules accept events up to 1 MB, or configure an EventBridge input transformer if a target enforces a smaller quota.