by
Join the DZone community and get the full member experience.
Join For Free An API Portal is one of the key architectural components of an effective
API Management strategy, along with an API Gateway. They work together
hand-in-hand. The API Portal allows developers to self-register and
learn about your API, while the API Gateway is the "sharp edge" of your
API Management solution, applying policies to API traffic in real-time.
Your
APIs cannot be a "Field of Dreams" ("if we build it, they will come").
Instead, you must ensure that your API Portal is engaging, and
facilitates developer self-service. This self-service starts right from
the get-go, where you must allow developers to self-register:
Of course, unless your organization happens to be Axway itself, you will want to customize the API Developer Portal. I've written before about how to customize the Axway API Portal using its own API (yes, the Axway API Portal has an API of its own), using stylesheets and JSON. In this way, you can apply your own look and feel.
This Thursday I'll be presenting a Webinar about the API Portal, explaining how it fits within an overall API Management strategy, and walking through a practical example. I'll walk through the process whereby a developer discovers an API in the API Portal, and then uses it in an Android app. I'll walk through the Android example, showing what it means to consume an API using a mobile app. Registration is free - here is the sign-up URL: http://www.axway.com/events/event/webinar-building-your-developer-portal-go-soa-api-economy
API
dev
Published at DZone with permission of Mark O'Neill, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments