Skip to main content

Developer Portal API Usage Request/Approval

Overview​

Once API Products are published, developers can request access to use them via the Developer Portal. This tutorial explains how administrators can view, approve, or reject these requests in the APIM Console. It also shows how to review linked product settings and check approval reasons.

Prerequisites​

To perform approval actions:

  • You must have Administrator access
  • Navigate to: Admin > API Usage Request Management
  • Products and applications must already exist in the system

Using the Request Management View​

The screen shows a list of all incoming API usage requests submitted by developers.

Columns Overview:

ColumnDescription
Request IDUnique ID of the request
Request DateTime when the request was submitted
Requester EmailThe user’s account email
Application NameName of the app requesting API usage
Product NameName of the product requested
API NameThe specific API being requested
RequestRequest note (e.g., reason for requesting)
StatusCurrent status of the request
ActionQuick access to review or process

Actions You Can Perform​

View Product Configuration:

  • Click on the Product name (e.g., mj-test-product-kong)
  • This will open the Product Detail Configuration Page, allowing you to review which APIs are assigned to that product

View Approval Status and Reason:

  • Click the status badge
  • A popup or modal will appear showing:
  • Whether the request was approved or denied
  • The reason entered during the decision (e.g., “insufficient authentication”, “approved after review”, etc.)

Currently, the page does not support inline editing or bulk approval. You must handle approvals through the product configuration page or an API-level permission system.

Best Practices​

  • Review the Application name and Requester email to ensure legitimacy
  • Keep your product configurations up to date so the approvals reflect accurate API scope
  • Respond to all requests promptly to ensure developer satisfaction
  • Periodically audit denied requests for patterns in rejection reasons