Date of version: November 1, 2021

New Features

📣  The first version of Apinizer API Developer Portal has been released!

API Portal is an important communication channel for API, it acts as a bridge between API Provider and API Consumer. API Provider defines API Proxies that it wants to open to the outside world from Apinizer Manager Console. API Consumer manages how it can communicate to an API through the Apinizer API Developer Portal. The aim is to enable the API Provider to easily publish and consume API Proxies.

Additionally, Apinizer provides design customization on the API Developer Portal, accessing and testing API Catalog and API Documentation, Terms & Conditions definition, API analytics, API traffic monitoring, account management, credential management, and API and Credential-based access control.

Portal API

Portal Manager can create API from API Proxy via administration section. Thus, external resources can access API Proxy through the assigned environment. It also manages the accessibility of the Portal Manager from here.

Portal Accounts

Portal Manager defines accounts with or without organization managers that can login to the API Developer Portal. The account, which is the organization manager, has the authority to create other accounts belonging to its sub-organizations. The account can manage or assign APIs assigned to it to another account. Each account sets its own credentials that send requests to the API. In addition, credential-based API access control or API-based credential access restriction can be made.

Portal Settings

Portal Manager configures customisation, email management, terms & conditions and integration processes that apply throughout the portal.

Important Enhancements and Modifications

  • The application logs of the worker can be audited through Application Logs tab on the API Proxy screen.
  • Management of historical information of Credential and API to be used by Portal UI has been added to Audit Logs.
  • CorrelationID filter is added on API Traffic screen.

Bug Fixes

Issue No



Although the credential is removed from the contract, its relationship is visible.


Every object is not audited.


The credential in the expired contract is able to request and does not give "Contract Expire Date ..etc" error.

APNZ-2605WS-Security policy gives an error.

Deleting and filtering operations do not work consistently on Application Logs screen.


Audit pages/tabs do not open.

APNZ-2609Project filter does not work in ACL tab on Credential. The same API Proxy can be added to the credential more than once.

When logged in, the project acts as if it is not even though it is selected.


If a parameter is used in more than one place in DB-2-API, an error is received.


Although the option to add user to the header is active in JWT Authentication policy, there is no header added in log.


Authentication token receiving error does not appear in token logs.