The end user guide varies depending on the type of frontend application that you deployed for the developer portal. This guide includes steps for the sample React app and Solo’s Backstage frontend plugin. If you created or modified your own frontend app, adjust the guide accordingly.

Before you begin

Before giving your end users the developer portal, make sure that you completed all the setup tasks, including the following.

  1. Install and make sure that the portal is healthy, including the portal, external auth, rate limiting, and Redis components.
  2. Create your API products.
  3. Prepare usage plans for your API products, including external auth and rate limiting policies.
  4. Configure the developer portal, including to expose the portal server securely.
  5. Create a frontend for your developer.

Discover your API products

End users can discover API products in your developer portal that they have access to.

  1. To launch the developer portal, your end users enter the hostname that you exposed the portal on, such as, in their web browser.
  2. By default, end users can review the home page. They can see any APIs that you did not require authentication for via external auth policies. If you followed the steps in Configure the developer portal, the tracks and petstore API products are included in the portal. However, only the tracks API is publicly available and can be seen when selecting APIs from the menu bar. The petstore API is set to private and can only be seen after the user logs in to the developer portal.
  3. To review private APIs and perform other actions, such as to create an API key, the end users click Login. They are redirected to the OIDC provider that you configured.
  4. After successfully logging in, the end users can see the public and private APIs that they have access to.
  5. Users can select an API product to see the OpenAPI specification for that API in Swagger or Redoc format. They can review details, such as the API schema, required request parameters, response body information, or supported HTTP response codes.

View usage plans

End users can view the usage plans in the developer portal that you set up for your API products.

Create an API key to use the API products

To interact with APIs that require API key authentication, end users can use the developer portal to create an API key.

  1. Follow steps 1 - 3 in View usage plans.
  2. Select the API product to create an API key for.
  3. Click Add Key.
  4. In the pop-up window, enter a name for the API key and then click Generate key.
  5. Copy and store the generated API key value in a secure place. Keep in mind that you cannot review the API key value anymore after you close the pop-up window.

Great job! You just created an API key for a usage plan for your API products. To verify that the API key works, try out an API.

Try out an API

To access an API with the API key, users can review the API docs for a product and send a request to an API via the Swagger try-it-out feature.

  1. Click the APIs tab.
  2. Select the API product that you want to try out.
  3. Toggle the Swagger View.
  4. Click Authorize.
  5. Paste your API key value into the Value field, and then click Authorize.
  6. Click Close to return to the list of APIs in the API product.
  7. Expand the API that you want to try, such as Get /trackapi/tracks, click Try it out, then Execute.
  8. Review the server response details, or copy the curl command to try it out in your own environment.

Delete an API key

End users can use the developer portal to remove API keys that are not used anymore.

  1. To view API keys, follow steps 1 - 3 in View usage plans.
  2. Select the API product and usage plan for which you created the API key and then find the API key that you want to remove.
  3. Remove the API key. The steps vary depending on the frontend application for the developer portal.