Dev Portal Based on Management APIs

[#1]

It appears Apigee advertises two out-of-the-box solutions, a Drupal and Markdown based versions. However, it appears Apigee offers a third solution, which is to leverage the Management APIs.

What are the arguments against using these APIs to build a fully customizable developer portal in order to fit my organization's needs (besides the obvious which is that it just works without any significant configuration)? Is there a reason these APIs are not advertised on the same level as the other options?

[dchiesa1 · Accepted solution]

You're right - there are three options for dev portal. All of them interact with the Apigee Edge system via management APIs.

1. The easy-to-use, click-to-provision devportal.
2. The fully customizable Drupal devportal. This relies on the PHP SDK (library) for Apigee Edge
3. Do-it-yourself

We at Apigee support all of these options. (regarding, "these APIs are not advertised". We don't really advertise.)

The Admin APIs are fully documented. As you said, it will take some work to custom-build something on your own.

Many customers use these APIs to integrate key and credential provisioning for Apigee Edge into their existing portals.