Send Docs Feedback

Creating a developer portal

This topic describes how to create your portal. With the exception of the "Request your portal" section, this topic applies to both cloud and Edge for Private Cloud customers.

Request your portal (cloud only)

You must have an Apigee Edge account, as described in Creating an Apigee Edge account.

This section applies to cloud customers only. If you're an Edge for Private Cloud customer, you'll install and configure your own portal. For information on where to download the product installers, see the Apigee Release Notes.

If you're a cloud customer, complete the developer services portal request form to request your developer portal. You must provide your organization name and email address. If you don't know your organization name, sign in to and select your username > User Settings. In the User Settings window, you can see your organization name.

After you request the portal, an Apigee representative will respond with more information, typically within one or two business days, but it may be as long as five business days. The response will contain links to your portal, a ready-to-use Drupal instance with the following default pages: homepage, Blog, Forum

(Apigee Edge customers on paid accounts receive multiple sites with duplicate portal environments: Dev, Test, and Live.)

Log in to your portal

The URL to your portal will be in the form of: 


For example, for the dev version of the myorg portal:

When you log in with the administrator credentials you're given, you'll see something like this:


  • Menu items for the pre-built Blog and Forum pages.
  • A Drupal administration menu only available to Drupal administrators of your portal. This is where portal administrators perform much of the site's configuration. 

If you click the Apigee logo on your portal, you'll get to the home page.

Configure the connection between the portal and Edge

The portal acts as a client for Apigee Edge. That means the portal does not function as a stand-alone system. Instead, much of the information used by the portal is actually stored on Edge. When necessary, the portal makes an HTTP or HTTPS request to retrieve information from Edge or to send information to Edge.

There are three pieces of information that the portal needs to communicate with Edge:

  • URL of the Edge endpoint

    The default endpoint for the cloud-based version of Edge is

    For Private Cloud installation, the URL is in the form: http://EdgePrivateCloudIp:8080/v1​ or https://EdgePrivateCloudIp:SSLport/v1.

    Where EdgePrivateCloudIp is the IP address of the Edge Management Server server and SSLport is the SSL port for the Edge management API. For example, 8443. 
  • Apigee organization name

    This is the name of your organization on Edge. You set up the organization when you create your account on Edge. 
  • Username and password of a developer administrator

    The calls from the portal to Edge are authenticated and require a user with Developer Administrator privileges.

    It is recommended that you create a user with Developer Administrator privileges exclusively for connecting to Edge from the portal to minimize the risk that the user will be deleted. If the designated user is deleted on Edge, then the portal will no longer be able to connect to Edge. 

To view the connection information:

  1. In the Drupal administration menu, select Configuration > Dev Portal Settings.

To change the configuration:

How you change the configuration depends on your portal installation and portal version:

  • Cloud-based installation of portal version 15.01.06 and later: You must make a request to Apigee Support to change the connection information. For example, if you want to change the name of the organization.
  • On-premises installation and cloud-based portal previous to version 15.01.06: Change the connection information as described below:
  1. In the Drupal administration menu, select Configuration > Dev Portal Settings.
  2. Enter your organization name in Management API Organization.
  3. Enter the URL of the Edge endpoint in Management API Endpoint URL.
  4. Enter the organization administrator credentials in Endpoint Authenticated User and Authenticated User's Password.
  5. Select Test Connection to make sure the connection is successful.
  6. Select Save Configuration.

Create admin users

If you want to add more administrators to your portal:

  1. In the Drupal administration menu, select People > Add User.
  2. Enter the required information about the new user, and provide a temporary password.
  3. Be sure to select Active and administrator. To have an automatic email sent to the user with a link to the new portal, select Notify user of new account.
    When a new administrator logs in, he or she will have the same administrator rights as you.

Configure an SMTP server

The developer portal requires that you configure an SMTP server to send email messages. To configure the SMTP server, you must first enable the Drupal SMTP Authentication Support module on the developer portal.

See Configuring email for more.

Configure your portal

Drupal runs almost entirely on modules—self-contained code plug-ins to the Drupal framework. Anything you do or configure in Drupal is controlled by a module, from menu control, to layout configuration, to reports. To see a list of modules that are installed in your portal, select Modules in the Drupal menu.

To start configuring your portal, see Add and edit content.

Create API products

Before you send developers to your portal, be sure you have API products (bundles of APIs) to select when they create apps on your portal. For more information, see Create API products.

Send developers to your portal

When your portal is ready for public consumption, start sending developers to it. When they register, they're added as simply "authenticated users" (not Drupal administrators), and their user information is automatically added to Drupal—and to your environment, where they are registered as "developers". When developers register apps in your developer portal, where they select API products to use in their apps, those apps are also registered on your site. Your developer portal and enterprise site are connected.


Help or comments?