Chapter 8: Message Transformations

You have now learned how API Connect (APIC) can quickly and easily be configured to organize, socialize, analyze, and provide a secure gateway to your existing APIs. Hopefully, you have seen the tremendous value in using it to expose your existing APIs where the request and response messages are simply passed to/from the backend API that is being proxied. There may be times, however, that the request and/or response messages will not be what the consumer is passing and the backend API is expecting. Or perhaps you wish to modernize an existing backend service by exposing it as a RESTful API. Take, for example, an existing SOAP Web service that you wish to expose as a RESTful API to your consumers. Or maybe you will just need to enrich or redact certain data within the request/response messages. There are many reasons why you might to alter the request and response data as it passes through your API. This is where API Connect provides many options depending...