{"id":110755,"date":"2016-10-16T10:58:06","date_gmt":"2016-10-16T17:58:06","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/early-october-updates\/"},"modified":"2016-10-16T10:58:06","modified_gmt":"2016-10-16T17:58:06","slug":"early-october-updates","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/early-october-updates\/","title":{"rendered":"Early October updates for Microsoft Flow"},"content":{"rendered":"

In the past two weeks we’ve introduced a few new features to improve the connectivity and power of Microsoft Flow.<\/p>\n

Custom APIs support more authentication types<\/h2>\n

Custom APIs are the way to extend what Microsoft Flow connects to (beyond our built-in connections). You can use Custom APIs to create flows that talk to almost any HTTP endpoint that supports JSON. However, getting authentication to work with Custom APIs can sometimes be a challenge. This is now easier with our improved custom API experience:<\/p>\n

\"\"<\/p>\n

First, custom APIs now support API Key authentication. This means you can define a header or a query string that will be sent on all of the requests to your API. Second, Custom APIs now can authenticate against any service that supports the full OAuth 2.0 specification. This requires you to provide:<\/p>\n