We are excited to announce the launch of the Health Graph Developer’s Console!
This console gives you a quick way to try various Health Graph API (@healthgraphapi) calls. You can specify all the request details, submit your request, and then see the results that are returned by the Health Graph platform.
To start using the console, you need to connect it to a Health Graph account. Follow these steps:
- Login to a RunKeeper/Health Graph development account. If you have registered one or more apps in the Partner Portal, you may wish to use that account. Note that we strongly recommend that development accounts not be team member personal accounts, since as part of development you will likely be updating and/or deleting data.
- If you need to populate your development account with some test data before you begin making API calls, click here for several methods for doing that.
- Image may be NSFW.
Clik here to view.
Launch the console by clicking here (you may wish to bookmark http://runkeeper.com/console for future reference). - Authorize the console to connect with your development account (this uses the same OAuth-based authorization mechanism that other Health Graph partner apps use).
Once you’ve successfully connected your account, you should see a console window showing all the request options that you can specify.
Image may be NSFW.
Clik here to view.
As you can see above, the default request values are for a request to GET your connected account’s /user resource. /user is the initial entry point for accessing any given user’s Health Graph account data. If you submit the default request, the Health Graph platform will send back the /user resource information corresponding to the specified access (“bearer”) token, in this case one of my test development accounts.
Image may be NSFW.
Clik here to view.
You can pass any valid Health Graph request in via the console. For instance, we can use the /user response to see what additional resources are available for this user, pick the /fitnessActivities resource, and then make a GET request to read the fitness feed.
Image may be NSFW.
Clik here to view.
If you’ve correctly specified your request, the Health Graph will respond with something similar to the following.
Image may be NSFW.
Clik here to view.
If you make an incorrect request, for instance by specifying the wrong content type that you’d accept back:
Image may be NSFW.
Clik here to view.
then you’ll receive an error response:
Image may be NSFW.
Clik here to view.
Note that the console supports using a */* wildcard for the Accept header content-type value. This enables you to make a request without knowing in advance what content type you’ll receive back in the response. This is particularly useful when you are exploring and learning the API, as you can note the content-type in the response so that will you know the correct value to use when creating your own application.
However you get to a correct request, once you have its response back, you can use the details to continue accessing and processing Health Graph data. That’s all there is to it!
For a quick overview of what Health Graph API operations are available, you may wish to read through this “Health Graph Hacking 101” presentation. For more details on the various resources available to GET, PUT, and POST to as part of the Health Graph API, please refer to the full Health Graph API documentation.
We hope this console proves useful as you explore and prototype with the Health Graph API. And we’d greatly appreciate any feedback you have for how we can make the console even better.
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
