Phidiax Tech Blog

Recently, we were tasked to update our client's BizTalk 2013 application to use AssureSign. One of the main steps is to enhance BizTalk to receive a notification from AssureSign once the document is signed. This blog is part of a 3-part series to accomplish integration between AssureSign and BizTalk utilizing Azure Services like Logic Apps to facilitate the transaction.

1. Part 1 - AssureSign - Integration between AssureSign DocumentTRAK and Azure Logic App, as well as Service Bus
2. Part 2 - AssureSign - Integration between Azure Service Bus and BizTalk Server
3. Part 3 - AssureSign - API Management

With the Classic Azure portal, we know that we can create an ACS Service Bus external endpoint to receive the notification. However, our client is moving away from Classic Azure portal. Therefore, we've decided to use a Logic App request action to create an external endpoint. We also created a SAS Service Bus endpoint with a queue to hold the message for BizTalk to consume.

High-level Architecture

In this part 3, we focus on API Management

We learned while we tried to configure the Completed Document Transmission in AssureSign that the Service Endpoint (URL) can only accept the URL up to 129 characters length. 

However, the Azure Logic App service URL is much longer than 129 characters and there is no option to shorten the URL.  Therefore, we decided to utilize API Management so that we can have a shorter service URL for AssureSign to post to.

We use above Web API URL for the AssureSign's Service Endpoint (URL). 

Now, the complete workflow should work, and AssureSign DocumentTRAK Notifications will post from AssureSign, to API Management, to Logic Apps, to Service Bus, and finally to BizTalk.

1. Part 1 - AssureSign - Integration between AssureSign DocumentTRAK and Azure Logic App, as well as Service Bus
2. Part 2 - AssureSign - Integration between Azure Service Bus and BizTalk Server
3. Part 3 - AssureSign - API Management