07 Jun Fatsecret api integration issues and gethealth as its remedy
Fatsecret provide a REST-like API that allows developers to integrate FatSecret Platform features into their applications. The REST API can be used to build nutrition, diet and weight management solutions on any platform, including desktop client applications and mobile device solutions.In this blog post, I will touch down what issues you can face while integrating Fatsecret API. It uses Oauth 1.0 for user authentication. The main goal of gethealth.io is to save all this developer time which he can put building the business logic of application, while forgetting about all the technicalities of integrating and fetching the data. It’s done by using Unified gethealth.io REST API across hundred’s of devices and applications
Step 1: Register application to API consumer key and secret which allow apps to connect.
Once you’ve registered you’ll be able to start making calls to the API.
Step 2: Read Documentation of API
FatSecret Platform, Uses OAuth 1.0. The REST API requires that developers use the OAuth protocol for securely signing all requests. There are two types of request that the REST API Supports:
Further more you need to be well versed with the Oauth 1.0 to handle the authentication and api request generation to fatsecret platform. The below diagram shows the authentication flow of oauth 1.0.
Step 3: Find an OAuth 1.0 library for your programming language and framework to create an authorization flow.
Depending upon the programming language you use , you can need to find the appropriate library which supports Oauth 1.0 authentication mechanism and flow.
There are some libraries suggested by Fatsecret on there page which provides the higher level abstraction for connecting users and making signing requests.
Step 4 Generating request to get data from Misfit Cloud API
The Fatsecret Platform REST API is the primary way to get data in and out of Fatsecret platform. It’s a low-level HTTP-based API that you can use to query data, post new stories, upload photos and a variety of other tasks that an app may need to do. Most API calls must be signed. The basic steps involved in correctly signing and making requests are as follows:
hese steps described above can take considerable developer time and also will let developer to focus on the business logic of application. Gethealth.io can help you in this regard. Get health provides all this with few REST API calls. Using gethealth.io you need to follow below steps
Step 1: Signup for gethealth.io
Step 2: Integrate our Rest API.
For user authentication we have provided the REST API call which you just need to integrate in your Application and it handles all authentication mechanism itself (e.g Oauth 2.o for fitbit). Note before authentication of user you need to create that user account within gethealth.io so we can track there authentication access codes.
Step 3: Make API requests with user authorization token to fetch data across multiple user or single user.
We also provide Rest API calls which enable you to fetch data across multiple user using account call and for particular user using user call.Checkout out API documentation which let’s you get starting using the API in no time. The below image shows the quick-start guide which you can get after signing up.
In this blog post I described the steps which you need to deal with while accessing data using Fatsecret platform and also described how simply we can use gethealth.io to get the same data while reducing all the technical effort by the developer. Using gethealth the developer can focus on how he can focus on the data fetched from source. Also using gethealth developer can add data from hundreds of sources like misfit, Runkeeper, Strava and many more wearables and healthcare application using same implementation flow and need not to follow each sources development requirement. In coming blogs I will post interesting integration challenges about Runkeeper, Googlefit and other application. Follow gethealth.io on twitter.