Thanks to everyone that provided feedback on our previous expansion of user data export, we have pushed an update so that it now also supports:
- Heart rate information in exported activity GPX files
- Start/stop in GPX for all activities where the user paused and then resumed their activity
Heart rate information is included with each GPS data point via
gpxtpx:hr tags, while each pause/resume results in a new
One question we often get from developers new to the Health Graph platform is “How can I create test data?”. Here are some ways you can get up and running quickly.
After you request developer Health Graph access, you have automatic read access to any data in your developer account. You can take advantage of that by using various free Health Graph apps to add data to your account. For example, you can record or manually enter:
- Fitness activities using our RunKeeper app (iOS | Android | Windows Phone).
- Sleep information with GKSleep (web app) or Sleepy (Android).
- Nutrition information via GKNutrition (web app).
- Weight data using Weighty (iOS) or the “Body Measurements” update widget on the lower left of your RunKeeper homepage (web app).
Another way to add data to your developer account is to use an existing non-development account and Street Team tagging.
You can copy existing fitness activity data into your developer account by:
- Logging into an existing non-development account containing fitness activities.
- Adding your developer account as a Street Team member in your non-development account; you’ll need to make the request from the latter and then approve it from the former.
- For each activity you wish to copy from your non-development account into your developer account, tag the developer account from that activity’s page; this copies the activity data into your developer account.
- Optional: When you’re done tagging and copying data, you can remove the tags while in your developer account, then remove your non-development account from your developer account Street Team, to sever the linkages but keep the copied data.
One more option: You can export an existing user’s data (click here for details) then parse that data and write it back into your own developer account via the Health Graph API. In fact, doing so is very instructive as it requires you to explore several different aspects of the Health Graph platform.
The above options should give you plenty of ways to get test data together for your application. I hope this helps and happy health hacking!
We recently made a change to developer Health Graph read access.
Developers can now read data from their own app registering account, the one they listed when they submitted their app registration in the Partner portal, without needing to apply for special Read permissions. This automatic read permission lets one begin using the full Health Graph API immediately against their own data.
To make certain everyone is clear on what the change enables, let’s define “registering account” as the account under which an app is registered. Then as far as permissions are concerned, the new rules for Health Graph data requests are as follows:
- A read request for the registering account succeeds
- A read request for a non-registering account succeeds if and only if Special API Read permissions have been requested and granted
- A write request succeeds
Note: To read from any other Health Graph account, apps still need to make a request for and be granted the Special API Read permissions. Also Health Graph API Policies remain unchanged.
We hope this helps you get going faster on new Health Graph projects.
While this post is targeted at attendees of the 3-5 March 2012 AngelHack developer events, even if you’re not attending you still might find some useful Health Graph information and development tips.
Whether you’re reading this in Boston or San Francisco, you’re in for a great weekend of hacking, networking, and fun. And who knows, maybe even a great prize at the end!
First up, here’s a copy of the Health Graph programming primer we’re presenting onsite to get you going (click through the presentation and note that links are live):
More details on some key points:
You can access a technical overview of the RESTful Health Graph API by clicking here.
All Health Graph partners are required to follow the Health Graph API Policies.
When you’re ready to get started building a Health Graph API application, visit the RunKeeper Partner page and click “Connect To Our API“. From there you can fill out the form to register your new Health Graph integrated app, service, or device.
Click here to learn about authorization removal callbacks before providing your callback URL on the form. If you will be reading data out of the Health Graph for accounts other than your own app registering account, you should also request Read permission on the form, being sure you give a detailed explanation of what you will do with that data once you’ve accessed it.
Note: Please include the appropriate city-specific hashtag,
#angelHackBOS, in your new application description and Read permission justification so we can address your request as quickly as possible.
Need some inspiration to get your developer juices flowing? Check out some of the applications built and deployed using the Health Graph API, available from the RunKeeper Apps page (click here). You can also access an archive of third party libraries, wrappers, and bindings which might make your Health Graph API-based development easier by clicking here. And there’s more information on how app and library partners are taking advantage of the Health Graph via our Health Graph partner profiles series on the blog.
When you encounter issues, you can ask questions and join in the developer conversation by visiting the Health Graph discussion group. You can file issues in our support form. You can also reach our team on Twitter, Facebook, and Google+.
Related content that may also interest you:
- Click here to learn how to export your own user data from the Health Graph; useful for backups as well as parsing your data to re-upload into a test account via the Health Graph API.
- The Healthy button allows you to easily embed the ability to share health and fitness related content on your site or blog into Health Graph users’ FitnessFeeds; click here to learn more about the Healthy button
Now that you know how to use the Health Graph, go build something great and win this thing! Happy hacking!