Page History
If a user wants to consume a Private API, he must first register for it (refer to Subscribing to Private APIs). If approval is required for the API he wants to subscribe to, the user has to wait for an API Management user with approval authorization to answer his request. On this page, we explain the approval process and its options.
| If a user has signed up for an API that needs approval, a corresponding note is displayed when he finished the signup wizard. | ||||||||
| He will also get a notification in the API Developer Portal (refer to Notifications). The user must now wait for his request to be processed.
| ||||||||
| At the same time, all API Management users that have permission to answer approval requests get a notification that a new request arrived. A click on the notification... | ||||||||
|
Approving a Request
| The approver must click the Approve button if he wants to enable the requester to use the API. | ||||||||
|
| ||||||||
| The contract is marked as Approved. | ||||||||
|
| ||||||||
| In the My Clients section, the necessary information to use the API is now displayed. The API is ready to use. |
Rejecting a Request
| The approver must click the Reject button if he does not want the requester to use the API. | ||||||||||
|
| ||||||||||
| The contract is marked as Rejected. | ||||||||||
|
| ||||||||||
| In the My Clients section, the corresponding client is still displayed.
The user has two options to handle a retired contract:
|
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
|
| Otp | ||||
|---|---|---|---|---|
|
...
Overview
Content Tools