Skip to main content
Commerce V1 uses the CloudEvents 1.0 specification for asynchronous service-to-service communication. Events flow between Commerce and your extension services and processor integrations via the mTLS-secured event bridge.
Diagram showing the Cloud Event Bridge architecture in Commerce V1

​
Event Envelope

All events follow the CloudEvents HTTP binding with these required attributes: Commerce also requires these extension attributes: Commerce sets both on outbound events. Set them on every inbound event you send, using the values from the Commerce event that triggered it. ce-idempotencykey is optional. Commerce processes each key once and ignores redeliveries with the same key. Without it, Commerce processes every delivery, including duplicates.

​
Inbound Events

Events sent to Commerce by your integration services.

​
Outbound Events

Events sent by Commerce to your integration services.