Breadcrumbs

Answering Approval Requests

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.

note_awaiting_approval.png

If a user has signed up for an API that needs approval, a corresponding note is displayed when he finished the signup wizard.
note_pending_approval.png

He will also get a notification in the API Developer Portal (refer to (23.1.1) Notifications).

The user must now wait for his request to be processed.

The notifications can also be sent by by email. This feature must be enabled during the the setup of your Scheer PAS installation. Ask your Scheer PAS administrator for help.
admin_note_approval_request.png

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...
api_contracts_tab.png

... opens the Contracts tab of the corresponding API.

Two buttons are shown for the pending request:

Approving a Request

approve_request.png

The approver must click the Approve button if he wants to enable the requester to use the API.
confirm_approval.png

For security reasons, the approver needs to confirm his choice.
contract_approved.png

The contract is marked as Approved.
note_approval.png

The user gets a corresponding notification in the API Developer Portal.
api_ready_to_use.png

In the My Clients section, the necessary information to use the API is now displayed. The API is ready to use.

Rejecting a Request

reject_request.png

The approver must click the Reject button if he does not want the requester to use the API.
rejection_message.png

For security reasons, the approver needs to confirm his choice.

He can also insert a personal rejection message for the user. This is optional and will only be sent to the user if the email notification feature is enabled.
contract_rejected.png

The contract is marked as Rejected.
note_rejection.png

The user gets a corresponding notification in the API Developer Portal.
client_retired.png

In the My Clients section, the corresponding client is still displayed.

  • If the used client already contains other contracts, the rejected contract is just not part of the list.

  • If the used client does not contain any other contracts, it is displayed as Retired.

The user has two options to handle a retired contract:

  • Use the Remove client icon to delete the unused client.

  • Use the Register client icon to register the client. You will then be able to reuse it for further contracts.
Related Pages: