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.

[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.

[lizlynch · Accepted solution]

Hi,

Thanks, Dino!

Darren, you raise a good point and I've added a section to the docs to draw attention to this option:

Create a custom portal using Apigee Edge management APIs

Thank you for raising this! 🙂

Liz

[sasikumarchenni]

We are trying to publish integrated developer portal and wanted to understand following requirement.

1. Management API for integrated developer portal management, publish products, update audience, update visibility of each product

2. Apigee integrated developer portal with third party identity provider for authentication. During logout, apigee logout request has relay state more than 80 characters and relay state is not url encoded. So, logout operation fails. Any solution ?

3. For every product we can attach one spec but every product may have more than one API. How do we maintain the SPEC when there is a more possibility to add new API to the product or remove them from product ? does that mean every time we have to update the spec ?

4. How to we start with security scope ? how to we enable progressive development since we have narrowed scope during initial phase of Oauth API proxies.

Please assist.

[karlscheirer]

You might have better luck posting this question in the Integrated Portal space: https://community.apigee.com/spaces/175/index.html.

This space is dedicated to questions about the Drupal-based portal.

[chaudharyvaisha]

Have you built the custom portal using management APIs?
We have the same requirement to build developer portal using react.js and management APIs. But how the user(developer) management would be done? What all APIs are needed in the process is what I am looking for.