API clients deserialize incoming payloads into domain objects the application can use. The payload may arrive in a response, reply, or consumed event, and its data model must conform to the service’s schema. section 8.1.7
Client DTOs can be untyped structures, handwritten classes, code-generated classes, or libraries provided by the service team. For text-based formats, teams can choose between these approaches; binary formats usually use code generation. A client may model only the message types or fields relevant to its responsibilities. section 8.1.7
Figure 8.3 An API client must have a data model of the messages that it exchanges with the service. The data model must serialize and deserialize correctly as defined by the schema. It can either be untyped (e.g. hash maps) or consist of handwritten or code-generated classes.
Compare untyped data models with handwritten and code-generated classes for representing API messages. section 8.1.7










