Skip to main content
Every example below is one complete HTTP request body. Each request contains one direct CloudEvents 1.0 structured JSON event; no fields need to be prepended or reconstructed. Values are fictional but production-shaped. Monetary components use USD integer minor units and always include subtotal, discount, shipping, tax, and total—even when a component is zero.

order.created.v1

order.paid.v1

order.payment_failed.v1

order.canceled.v1

order.fulfillment_queued.v1

order.fulfillment_submitted.v1

order.fulfillment_accepted.v1

order.fulfillment_rejected.v1

order.shipped.v1

order.fulfilled.v1

order.fulfillment_failed.v1

Bulk catalog operation

These three events share the same correlationid and batch_id. The item and package events remain independently useful, while the batch event summarizes the whole operation.

catalog_item.changed.v1

package.changed.v1

catalog_batch.completed.v1

storefront.changed.v1

destination.test.v1