Site iconAxway Blog

Amplify Central Unified Catalog API subscription approval flow using API Builder and MS Teams

Amplify Central Unified Catalog API subscription approval flow using API Builder and MS Teams

In a prior blog post we described how to use Axway’s API Builder to create an Amplify Central Unified Catalog API Subscription custom approval workflow that leverages Salesforce.

In this blog post, we’ll describe a new API Builder-based API subscription approval workflow that leverages Microsoft Teams for approving the request as follows:

API Builder Project

The API Builder project exposes two API’s:

Its flow is shown below:

These APIs are created in an API-First fashion with the OpenAPI Specification (OAS) documents created in Stoplight in the following two repos:

The APIs are secured with API Key authentication in a header with key apikey. The API key value is set as an environment variable.

A complete list of environment variables for this project is shown below:

CLIENT_ID=<YOUR AMPLIFY SERVICE ACCOUNT CLIENT ID>
CLIENT_SECRET=<YOUR AMPLIFY SERVICE ACCOUNT CLIENT SECRET>
API_KEY=<AN API KEY THAT YOU SET>
MS_TEAMS_WEBHOOK_URL=<MS TEAMS INCOMING WEBHOOK CONNECTOR URL>
API_CENTRAL_URL=<YOUR AMPLIFY CENTRAL URL>
BASEURL=<THE BASE URL OF YOUR API BUILDER API>

The API Builder project can be found on GitHub.

A Docker Container image can be found on Docker Hub.

Summary

In this Amplify Central Unified Catalog custom API subscription approval workflow example we saw how API Builder can respond to subscription requests, integrate with Microsoft Teams to present an approval form to the API Approver, and update the request based on the approvers action.

Need help with API Builder? Extend your skills with Axway University.

Exit mobile version