Hi Bob, This is usually solved at the application layer with a BUS doing this API composition. Then APIMan would expose that API instead of the multiple internal APIs. If apiman was combined with Fuse or camel, this could be done, but I do not think that would be an easy feature. Usually is best to place that logic into a BUS layer, and then expose that service as well as an aggregated service, this way you could expose all the single services and the aggregated one. Cheers, 2015-01-22 13:06 GMT+01:00 Eric Wittmann <eric.wittmann(a)redhat.com <mailto:eric.wittmann@redhat.com>>: Hi Bob, thanks for the question. I have CC'd the apiman mailing list in case the answer is interesting to others. Hopefully I understand the question, which is around aggregation of various disparate APIs into a single application specific API. I think that apiman does something similar to what you are suggesting, in that all API endpoints end up going through the API Gateway rather than directly to the various disparate services. In other words, if a single application may consume N different services provided through apiman, *all* of those services are ultimately consumed through the root API Gateway endpoint (e.g. http://gatewayhost.com/api-gateway/*). That isn't quite the same as creating an application-specific API, but is perhaps functionally equivalent. At the moment we do not have any specific plans to implement API aggregation in apiman, but if there were community interest in it then we would certainly consider adding it to the roadmap. :) -Eric On 1/21/2015 1:44 PM, Bob McWhirter wrote: > Heya Eric— > > So I’m looking into Microservices, and one thing that always pops up is an "API Gateway” which might consume N services and expose them as a single service. > > The use-case being that while a fat application (desktop, web, etc) might talk to 15 different services, something on a constrained network (such as Mobile) would rather have an application-specific API that handles aggregating some subset of those 15 services into a single service, reducing round-trips. > > Is this a use-case planned for by APIMan? Or would APIMan be placed in front of an API Aggregator? > > Thanks! > > -Bob McWhirter > _______________________________________________ Apiman-user mailing list Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/apiman-user