Amazon EventBridge Webhook Payloads Now Up to 1 MB – What It Means for Your Shopify Apps

Shopify increased the Amazon EventBridge webhook payload limit from 256 KB to 1 MB, letting developers receive larger product and order data inline. Learn who is affected, how it works, and what steps to take now.

Amazon EventBridge Webhook Payloads Now Up to 1 MB – What It Means for Your Shopify Apps
6 sections

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

  • Fewer follow‑up API calls – Large product objects (e.g., a catalog with dozens of variants) now come in the webhook body, eliminating the need to immediately hit the Admin API for the full record.
  • Reduced latency – Inline payloads arrive in the same EventBridge event, so your downstream AWS Lambda or Step Functions can process the data without a second network round‑trip.
  • Simplified error handling – You still need to handle the rare >1 MB case, but the 1 MB threshold gives you a generous safety net for most real‑world use cases.
  • Downstream target limits – EventBridge itself caps entries at 1 MiB. Make sure any AWS targets (e.g., Lambda, SQS, Kinesis) are configured to accept events of that size, or use an input transformer to trim the payload before it reaches a smaller‑quota service.
  • What To Do – Actionable Steps

    Even though Shopify applied the change automatically, a quick audit will keep your integration rock‑solid:

  • Leave existing subscriptions untouched – Your shopify.app.toml file or GraphQL eventBridgeWebhookSubscriptionCreate calls continue to work. No version bump is needed.
  • Retain fallback handling – Keep code that checks for the { "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;

    }

  • Validate downstream AWS limits – In the AWS console, open your EventBridge rule and confirm the target (Lambda, SQS, etc.) allows payloads up to 1 MB. If not, add an input transformer that extracts only the fields you need, e.g.,
  • {

    "inputPathsMap": { "detail": "$.detail" },

    "template": "{ \"id\": <detail.id>, \"title\": <detail.title> }"

    }

  • Trim payloads when possible – Use include_fields on the subscription query to request only the fields your app consumes. This reduces the chance of hitting the 1 MB ceiling.
  • Monitor logs – Add a metric that logs when an event contains 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

  • Design for idempotency – Since fallback downloads are still possible, make your processing logic idempotent; the same resource might be delivered twice (once inline, once via download) during a transition.
  • Leverage `include_fields` – When you only need a subset of a product (e.g., id, title, price), request those fields explicitly. This keeps payloads small and speeds up downstream processing.
  • Cache fetched resources – If you still need to call the Admin API for occasional >1 MB objects, cache the response for the duration of the request to avoid duplicate API hits.
  • Test with edge cases – Simulate an order with >500 line items in a staging environment and verify your Lambda can handle a ~900 KB payload without timing out.
  • 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.

    Tags
    Sources

    Related Articles

    Admin‑Created Custom Apps Now Live in the Shopify Dev Dashboard

    Admin‑Created Custom Apps Now Live in the Shopify Dev Dashboard

    Shopify now surfaces custom apps built in the admin inside the Dev Dashboard, giving developers centralized credential control, IP allowlisting, and full API/webhook logs. Learn what changed, who’s affected, and how to secure and monitor your apps today.

    November 17, 20265 min
    Understanding the New B2B Location Access Rules in Shopify’s Customer Account API

    Understanding the New B2B Location Access Rules in Shopify’s Customer Account API

    Shopify’s latest API update tightens B2B location data access, limiting what customers can see to their own company information and orders. Learn what changed, who’s affected, and how to adapt your apps.

    November 17, 20266 min
    Unlock Custom Data Insights: Sidekick Now Analyzes Metafields & Metaobjects

    Unlock Custom Data Insights: Sidekick Now Analyzes Metafields & Metaobjects

    Sidekick can now read your store’s custom metafields and metaobjects, letting merchants ask analytics questions about fabric, supplier, designer and more. Learn what changed, who it affects, and how to start using this feature today.

    November 17, 20265 min
    Test Your Apps Early: Opt‑In to Admin API Token Expiry from the Dev Dashboard

    Test Your Apps Early: Opt‑In to Admin API Token Expiry from the Dev Dashboard

    Learn how to enable the new Admin API token expiry setting in the Shopify Dev Dashboard, why it matters for public apps, and step‑by‑step actions to test and validate your migration before the April 1, 2027 enforcement deadline.

    November 16, 20264 min