PuppyIP Resource Center
Cross-Border Ecommerce Development 4 min Published 2026-11-19

Shopify EventBridge payloads up to 1 MB: handle oversized deliveries

On November 17, Shopify raised the inline payload limit for Amazon EventBridge deliveries to 1,000,000 bytes. Existing subscriptions get the higher limit automatically. Above it, classic webhooks still send a resource ID, while Shopify Events sends an expiring download link. Keep both fallback paths and check the input limit of each AWS target separately.

Shopify Amazon EventBridge Webhooks Events

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The change applies to existing EventBridge subscriptions across supported API versions.
  • Measure the raw UTF-8 payload. Shopify's 1 MB threshold is 1,000,000 bytes.
  • For an oversized classic webhook, fetch the fields you need using its resource ID. For oversized Events, download the full payload before its link expires.
  • Verify AWS target input quotas separately from Shopify's limit.

Do existing subscriptions need a configuration change?

Shopify says the higher limit applies automatically to existing Amazon EventBridge subscriptions, including subscriptions configured through shopify.app.toml or the GraphQL Admin API. You do not need to recreate a subscription just to receive larger inline payloads. Some product or order messages that used to fall back above 256 KB can now arrive with the complete body.

Shopify measures raw UTF-8 bytes and includes payloads of exactly 1,000,000 bytes in inline delivery. Character counts can differ from byte counts, and JSON serialization affects size. When troubleshooting, measure Shopify's payload, the EventBridge envelope, and the input delivered to the target separately.

Handle classic webhooks and Events separately

An oversized classic webhook still sends just the resource ID. Identify this abbreviated delivery using the subscription topic and message structure, then use the authorized Admin API to fetch any additional fields you need. The read reflects the resource at query time. Do not treat it as a complete snapshot from the moment the original event occurred.

An oversized Events delivery instead includes a small payload with payload_url, payload_size_bytes, and expires_at. Look for payload_url before reading the fields you expect in an inline message. If present, retrieve the complete payload before expiry. Shopify treats the link as a short-lived credential, so keep the full URL out of logs.

Why a downstream target can fail after EventBridge receives the event

Shopify's 1,000,000-byte inline cap leaves room for the envelope under the EventBridge 1 MiB entry limit. Once the event reaches the bus, rules route it to specific targets. Target services, input wrapping, and a consumer's own size limits may still prevent an event that reached EventBridge from being processed.

Check the target's input quota and observed behavior in a test environment. If it only needs an order ID, an event type, and a few status fields, consider passing that subset with an EventBridge input transformer. Confirm that the transformation preserves routing information and keeps both overflow shapes distinguishable. It does not raise Shopify's inline limit.

Test four delivery shapes before deploying

Use synthetic data for a small message, an inline message between the former 256 KB cap and the new cap, an ID-only classic webhook, and an Events delivery with a temporary URL. Measure UTF-8 bytes and check the parser, what reaches the queue or target, and how the consumer handles duplicate delivery.

If the app needs only a few resource fields, consider include_fields for classic webhooks or a narrower subscription query for Events. Inventory the fields consumers actually read, then test inline and overflow behavior and watch follow-up fetch counts and target delivery errors.

Sources

Frequently Asked Questions

Do order webhooks with many line items still need an Admin API follow-up?

Check whether the classic webhook includes the fields the consumer needs. Fetch more data when an oversized delivery only has the resource ID and your workflow requires more fields. For Events overflow, use the temporary payload URL.

Does Shopify's 1 MB mean 1,048,576 bytes?

Shopify explicitly defines its inline threshold as 1,000,000 bytes. The EventBridge 1 MiB entry limit is separate and also has to accommodate the event envelope.

Does this raise the limit for subscriptions delivered directly over HTTPS?

The announcement specifically covers Amazon EventBridge. Consult Shopify's documentation for the applicable limit on other delivery channels.