I recently had the opportunity to work on an interesting project.

While most clients are content to manage their API landscape via Mule’s Cloudhub interface, one client was not.

In this particular case, they had a sophisticated internal portal that their administrators used and they wanted to offer said admins the ability to manage their APIs within that system rather than forcing them to navigate over to Cloudhub and learn a whole new user interface.

It came as no surprise that the Mule eats its own hay bales. All the power in that sexy Cloudhub UI is actually leveraging a rich set of API’s beneath the UI surface. It is these API’s that drive the functionality presented in the Cloudhub UI itself.

Of course, that means you don’t need to use Cloudhub if you really don’t want to. Any client can leverage these API’s and port all of Cloudhub’s power right into  its own user interface.

Now, as the saying goes, nothing worth achieving in life is easy. There were challenges to be sure. To port all of the required functionality into the client’s portal application took more than a set of commodity skills. The client was sensible, however, and did not appoint a team of ‘resources’ to fulfill the mandate — they sought out a Whisperer.

Two Whisperers, in fact. And within a few weeks, the client had ported the functionality it needed and had a rich set of MuleSoft API Manager features right inside its own internal bespoke portal.

It was pretty cool, if I say so myself. 

For the more inquisitive readers, here is the link to a list of the APIs on offer.