6.3.2 Configuring the API 6.3.3 Merging two application flows into a single API In this section we edit the API to include two different APIs from two microservices for the  same business function. From a consumer point of view, it looks like a single API but it is  actually connected to two different microservices at the back end.  We have now deployed the Commands swagger into the API Management service of API  Connect, either through the App Connect push functionality or through a direct import of the  API definition into API Connect. This API and Product now displays the command operations for the database (Add, Update,  Delete), but not the query (Read). We add this query manually by navigating to the API in API  Connect. 1. Navigate to the API Manager API Definition in API Connect for  database_operations  and  select  Paths  (Figure 6-40 on page 195) and the  /products  (Figure 6-41 on page 195)  path name. Figure 6-41 API definition in API Connect in Path Figure 6-40 API Definition in API Connect Chapter 6. Practical agile integration  195