{"id":18565,"date":"2018-02-28T15:00:00","date_gmt":"2018-02-28T15:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=18565"},"modified":"2019-02-14T20:18:29","modified_gmt":"2019-02-15T03:18:29","slug":"microsoft-flow-expose-public-apis-via-custom-connector","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/microsoft-flow-expose-public-apis-via-custom-connector\/","title":{"rendered":"Microsoft Flow: Expose Public APIs via Custom Connector"},"content":{"rendered":"

In this post we\u2019d like to highlight an article from Premier Developer consultant Megan Meyer<\/a>\u2019s blog where she walks us through setting up a Custom Connector in Microsoft Flow in order to access data from her FitBit device.<\/p>\n

\n

I love fitness trackers. I was excited to get the new Fitbit Alta HR, but some of my eagerness waned when I remembered why I hadn’t used a Fitbit since my old Fitbit One — I hated how it didn’t integrate with any of my other applications I used to track my information. Fitbit does<\/em> support some integration with partner apps<\/a>, but just not with any apps that I happen to prefer and use. <\/p>\n

[\u2026]<\/p>\n

Here’s the thing — all of these fitness services provide APIs to interact with their data. All I need to do is write something to make them all talk to each other. I want to achieve a few things; my solution needs to be: <\/p>\n