POST. There is no Batch Relay wrapper around the CloudEvent.
Configure destinations and select available topics in the
Developer Dashboard. The dashboard also
shows delivery history and any topic references available to your account.
Contract authority
The live AsyncAPI document is the canonical public event contract:/specs/events-v1.asyncapi.json, but an
integration should retrieve or pin the live canonical document for release
validation.
Direct CloudEvent payload
Every request hasContent-Type: application/cloudevents+json and a JSON body
like this:
data carries the
topic-specific business fact. origin identifies how the fact entered Batch
Relay (storefront, developer_api, or system); it is not a transport
channel.
When an event defines monetary summary fields, all five components are present:
subtotal_minor_units, discount_minor_units, shipping_minor_units,
tax_minor_units, and total_minor_units. Values are non-negative integers in
USD; an inapplicable component is 0, not omitted.
Delivery semantics
- Delivery is asynchronous and at least once. A receiver can see the same CloudEvent more than once.
- A
2xxresponse acknowledges the delivery. Any other response, timeout, or network failure is eligible for retry. - Retry timing and delivery history are available in the Developer Dashboard; do not rely on an assumed retry schedule.
- Events may arrive out of order. Use
time,resourceversion, and your own durable state rules rather than arrival order. - One HTTP request contains one CloudEvent. Batch delivery is not part of V1.