A message is data exchanged between services through a message channel. It has a header of name-value metadata and a body containing the data in text or binary form. Headers can include a unique message ID and an optional return address for replies. section 8.3.1
Message roles include:
- Document: carries data for the receiver to interpret. section 8.3.1
- Event: reports something notable, often a domain-object state change. section 8.3.1
- Command: requests an operation, like an RPC request. section 8.3.1
A message contract describes its structure and the channel it travels through. AsyncAPI can specify message types and schemas alongside channel names and send-or-receive direction, supporting documentation, validation, and tooling across services. section 8.3.5
Customer-created event
An AsyncAPI definition can describe a CustomerCreatedEvent published to the com.example.Customer channel, with headers and a payload schema. section 8.3.5









