Azure App Services Series – Finding #2: Logic App Workflow API documentation is incomplete
This blog post is one of many of a series we have about Microsoft Azure App Services. See a list of all our findings here.
With the release of Logic Apps, Microsoft also releases the Workflow Management API. An API to use for getting access to the workflow of your logic apps allowing you to easily enable, disable workflows, get the status, etc.
Microsoft’s documentation of the API is incomplete and not clear which of the API calls are working in the current release of the API.
This API is allowing you to monitor Logic Apps with Integration Manager’s monitoring feature!
Problem #1: Incomplete documentation
According to the documentation the URI to the calls is:
This is wrong of course, you can clearly see that something is missing in the beginning of the URI.
It’s the URI to the region of the Logic App. For example: northeurope.logic.azure.com. The URI to call the API should look like this (example below):
Problem #2: Not all of the API calls documented are working (yet)
We did not manage to get many of the API calls to work. In fact, we only did manage to get one call to work – triggering the action by calling the /run method of the API. Most of the others (we did not test all) return 404 not found when calling the API.
Problem #3: There is no documentation about authenticating against the API
The documentation says nothing about how the authentication looks like, which makes the documentation somewhat useless!
For your interest, the authentication type supported is Basic. A username is created on logic app create which is ‘default‘ and the password to use is the primary key (not sure if the secondary works as well) which you can find in the logic apps properties blade of the Azure portal (see screenshot 1).
So the proper way of authenticating against the API is to send the Authorization header with your Basic username/password value – see example below:
Authorization: Basic YOURENCRYPTED(default:primaryAccessKey)