Weighty makes weight and fat percentage entry simple
Posted: June 12, 2012 Filed under: API, Apps, Community, iOS, iPhone, Libraries, Partners, Weight | Tags: activities, api, apps, cloud, data, fat, fitness, frankvanrest, healthgraph, ios, iphone, libraries, mobile, netherlands, partners, runkeeper, scale, triathlon, weight, weighty Leave a comment »Some of the best Health Graph (@healthgraphapi) partner apps are built to solve a developer’s own health and fitness issues. Case in point: Weighty, a free mobile app for quickly and easily tracking your weight and body fat percentage using the Health Graph. Weighty creator Frank Van Rest (@frankvanrest) talks about the problem he wanted to solve with his app, and how he went about creating it, below.
Bill Day: Please tell us about yourself and your work.
Frank Van Rest: I’m a Dutch mathematician who graduated in the summer of 2011. During my studies I founded a web development company. After graduation I was in need of a new goal, and getting a regular job wasn’t a great lookout after being an entrepreneur for eight years.
While traveling I decided to target doing a full Ironman triathlon in two years. I’ve always been a basketball player and couldn’t swim, so this was a challenge. But I’ve been in training for half a year now and am getting in quite good shape!
BD: What is the “elevator pitch” for why someone should use Weighty?
FVR: Weighty is a free iPhone app that makes it super easy to submit your weight and fat percentage to the Health Graph. Tracking your weight is a key step to effectively losing (or gaining) weight. I hope Weighty makes this easy and simple for everyone.
BD: How did you get started using the Health Graph API?
FVR: As I’ve gone about my triathlon training, I wanted to add my weight and fat percentage to the same place as my activities. This was previously only possible via the RunKeeper website, which is not as easily accessible as a mobile app when I’m standing on my weight scale.
The Health Graph API made it easy for me to create such a mobile app myself! I started with the iOS library I found on github and got it (after some debugging) to working pretty quickly. (Editor’s note: A complete listing of available third-party Health Graph libraries is available by clicking here.)
BD: How is using the Health Graph benefiting you?
FVR: The Health Graph makes it easy to create apps that submit data to a central health-related data repository. This cloud-based approach is very valuable for users, since combined analyses can be done. RunKeeper provides free publicity for my app by highlighting it in the Health Graph app directory and showing it in users’ FitnessFeeds when they submit their weight or fat percentage to the Health Graph.
BD: Which portions of the Health Graph API do you use, and why?
FVR: After authentication, I only use the API calls to POST weight and fat percentage. In the future I want to add historical data to the app, at which point I’ll also use GET calls to read that data back from the Health Graph.
BD: What do you like about the Health Graph? What would you like to see changed?
FVR: I like the ease of use of the API. I got a working version up and ready to test in a few hours of work.
During testing I found some small bugs in the API, but the API team fixed it quickly after contact. I’d like additional capabilities to remove and edit data records as well.
BD: If you could request any new feature from the Health Graph, what would it be? How would you use it?
FVR: My scale also gives water percentage and muscle percentage, which I would love to keep track of as well. If that were possible with the Health Graph as well, I’d implement in Weighty!
BD: Can you share any future plans for Weighty? What’s coming next that your users will be excited about? Does the Health Graph play a role in that, and if so, how?
FVR: Removing or editing weight or fat percentage records is not possible at the moment (not on the RunKeeper website and not via the Health Graph API). If a user makes a typo and enters the wrong data, it can really mess up their graphs and weekly averages. I would love to have the ability to remove records via my app (or the website). As soon as that’s possible, I’ll add historical data to the app, with the possibility to edit and delete that data as well.
BD: Is there anything else we should know about you or your application?
FVR: It’s a free iPhone app called Weighty and it’s available via
http://weighty.frisb.nl
. Please share your feedback via email to weighty@frisb.nl.
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Health Hack Day howto
Posted: May 18, 2012 Filed under: API, Apps, Community, Data, Events, Fitness, Hackathons, Libraries, Partners, Presentations, REST, Tools | Tags: api, apps, community, competition, contest, data, events, fitness, hackathons, hacking, healthhackday, json, libraries, oauth, partners, presentations, rest, restful, sensors, stockholm, teams, workshop Leave a comment »While this post is targeted at attendees of the 18-20 May 2012 Health Hack Day events in Stockholm, even if you’re not attending you still might find some useful Health Graph information and development tips. If you aren’t able to attend in person, you can also watch the livestream online.
Welcome Health Hack Day attendees and hackers!
You’re in for a great weekend of hacking, networking, and fun. And who knows, maybe even a prize at the end!
This post will walk you through the key information and procedures you need to use the Health Graph during the hackathon.
First up, here’s a copy of our Health Graph programming primer to get you going (click through the presentation and note that links are live):
More details on some key points:
You can access more technical details on 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. Likewise, if you would like to ask users for permission to retain their Health Graph data across deauthorizations, please request this permission on the form.
Note: Please include the official event hashtag, #hhd12, in your new application description and 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 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!

Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
OneHealthScore snapshots your health using the Health Graph
Posted: April 3, 2012 Filed under: API, Apps, Fitness, Partners, Running, Strength | Tags: api, consumers, fitness, healthgraph, jacobsattelmair, nutrition, onehealthscore, partners, partner_profiles, runkeeper, score, strength, weight, wellframe Leave a comment »Health Graph (@healthgraphapi) partner Wellframe (@wellframe) recently launched OneHealthScore. Read our interview with Jacob Sattelmair (@jakesatt) for more on how Wellframe is using the Health Graph to reframe the health discussion for consumers.
Bill Day: Please tell us about yourself and your work.
Jacob Sattelmair: I am the co-founder of Wellframe, the company behind OneHealthScore. We’re a health data science startup consisting of doctors, scientists, and engineers working to better leverage data to get people engaged in their health.
BD: What is the “elevator pitch” for why someone should use OneHealthScore?
JS: OneHealthScore is a Health Graph app that gives you real-time insight into how your physical activity impacts your health. Your score is based on the most advanced scientific research on the health benefits of physical activity. Keeping track of your score is a great way to stay motivated and make sure you are protecting your health.
BD: How did you get started using the Health Graph API?
JS: As our team’s first project, we were looking for an opportunity to apply scientific models to health behavior data in a way that would help people get new insights and be more engaged in their health. The Health Graph API was the most obvious place to start to achieve this goal.
BD: How is using the Health Graph benefiting your business?
JS: Using the Health Graph is a great opportunity for us to access motivated users’ health behavior data and experiment with new ways of making that data meaningful and motivational to them.
BD: Which portions of the Health Graph API do you use, and why?
JS: To start we are focusing on physical activities — fitness and strength activities to be specific — as we chose to first model the impact of physical activity on health. However, we may eventually expand our model to include other data types available through the Health Graph, such as weight and nutritional intake.
BD: What do you like about the Health Graph?
JS: We love the fact that the Health Graph enables users to collect their health data across a wide range of applications and devices, and then to consent to share that data with other applications and services that enable them to get more value from those data.
BD: Can you share any future plans for Your service? What’s coming next that your users will be excited about?
JS: We will continue to iterate on OneHealthScore, exploring new ways to give users motivational insights that encourage them to do and track more activities with RunKeeper.
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Support causes with Fitgiver and the Health Graph
Posted: March 22, 2012 Filed under: Apps, Community, Events, Fitness, Hackathons, Partners, Running | Tags: angelhack, api, boston, causes, charity, cycling, data, donations, fitgiver, fitness, geolocation, gps, hackathons, healthgraph, local, mit, rcolinkennedy, runkeeper, running, sponsor, startupweekend Leave a comment »The winner of our AngelHack prize for best use of the Health Graph (@healthgraphapi) was Fitgiver (@fitgiver) with their app enabling Health Graph users to raise money for the causes they love by doing the things they love to do anyway. One of Fitgiver’s founders, R. Colin Kennedy (@rcolinkennedy), took time out of a very busy schedule to answer a few questions for us. Take his experiences as inspiration to build great things at a hackathon near you, too!
Bill Day: Please tell us about yourself and your team.
R. Colin Kennedy: The Fitgiver team comes from a variety of backgrounds – some of us work at startups, some of us have a background in big business, and another is staff at MIT – but what unites us the opportunity that Fitgiver presents to create a meaningful impact.
BD: How did you get involved with AngelHack? And why did you decide to try out the Health Graph API?
CK: Well, a few of us ride bicycles together and had been kicking this around for a while. AngelHack was a great opportunity to move things to the next level. We had each individually done hackathons and Startup Weekends on other projects, and AngelHack promised a higher level of visibility, great prizes, and uniqueness because it was the first time running it in Boston.
The Fitgiver concept was tied to the Health Graph from its very inception. When we ride together, several of us use RunKeeper to track our activities. We knew that creates a data stream that is accessible and we thought we’d try and put it to use for causes we care about.
The beauty of it is that once users connect Fitgiver with their Health Graph account, they don’t actually have to do anything differently than they already were: Just use RunKeeper like normal, and we pull the data. [Editor's note: This should work with other Health Graph-based fitness activity tracking apps as well.]
BD: What is the “elevator pitch” for why someone should use Fitgiver?
CK: There are at least two different answers to that question.
First, our elevator pitch is that Fitgiver connects people and the causes they care about with organizations that want to sponsor them.
Second, users should consider Fitgiver because if they’re already going for a run or ride anyway, why not do some good while they’re at it?
BD: How is using the Health Graph benefiting Fitgiver? Which portions of the Health Graph API do you use, and why?
CK: The Health Graph makes data collection super easy. Currently, we’re using the workouts people track with RunKeeper. This is great because we also get the geo data, which we can use to verify that these workouts were real workouts, and at some point we’re thinking about localizing sponsorships so local businesses can sponsor local athletes. This really opens up a very powerful potential for both charities and small businesses to support people that are in their communities.
BD: What do you like about the Health Graph? What would you like to see changed?
CK: So far we’ve been really happy with the reliability and documentation with the API. It just works!
BD: Can you share any future plans for Fitgiver?
CK: We’re in talks with national health-related charities, and with sponsor companies that are looking like potential launch partners. Feedback has been so positive, we just have to keep going.
BD: Is there anything else we should know about your team or your application?
CK: We are all RunKeeper users and athletes, and have been so excited by the level of support that we’ve gotten from the RunKeeper team. Looking forward to furthering the partnership!
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Heart rate and pause/resume in user data exports
Posted: March 20, 2012 Filed under: Data, Fitness, Partners, Personal, Running | Tags: account, activities, cardio, data, developers, export, fitness, gps, gpx, gpxtpx, healthgraph, heartrate, measurements, partners, pause, quantifiedself, resume, revisions, runkeeper, tips, tracks, trkseg, user Leave a comment »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 trkseg.
If you’d like to try this out for yourself, please generate a new export and let us know what you think. Please leave feedback via my post to the Health Graph discussion forum (click here).
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Health Graph AngelHacking 101
Posted: March 3, 2012 Filed under: API, Apps, Community, Events, Fitness, Hackathons, Libraries, Partners, Plugins, Presentations, REST, Tools | Tags: angelhack, api, blood glucose, boston, competition, contest, cycling, diabetes, fitness, hackathons, health, healthgraph, hiking, json, nutrition, oauth, partners, prizes, promotion, restful, running, sanfrancisco, sensors, sleep, strength, swimming, training, walking, weight Leave a comment »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.
Welcome AngelHackers!
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!
This post will walk you through the key information and procedures you need to use the Health Graph during the hackathon.
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, #angelHackSF or #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!
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
User data export from the Health Graph
Posted: February 27, 2012 Filed under: Data, Fitness, Partners, Personal, Running, Sleep, Strength, Tools | Tags: account, activities, apps, background, cardio, csv, daily, data, developers, devices, diabetes, discussion, export, fitness, gps, gpx, healthgraph, measurements, nutrition, partners, photos, quantifiedself, revisions, runkeeper, services, settings, sleep, strength, tips, tracks, user, weight 1 Comment »We have updated the Health Graph user data export capability so that it now supports exporting all activities and all measurements from the user’s account. This includes data written into the Health Graph by partner apps, services, and devices in addition to RunKeeper’s app. Note that for activities which have an associated GPS track, those tracks are exported as well.
For users, this means they can export and backup all their health and fitness data whenever they like. For developers and self hackers, this also means they can download and manipulate their own user data as they see fit. We’ve had a number of requests for the latter, and we’re very glad to answer them!
More details on how the export works:
Initiate the export by logging in to your RunKeeper.com account settings page, scrolling to the bottom, and clicking on the “Export Data” link. Alternatively you can directly access the export form here:
http://runkeeper.com/exportDataForm
You then select starting and ending dates for the data you’d like to export, answer the captcha, and submit your request. Assuming you filled out the form correctly, once you click “Export Data” you’ll see a response indicating that your data is being packaged and will be delivered in a few minutes. You will then receive an email containing a link to download your data in a ZIP archive.
The ZIP contains cardioActivities.csv and measurements.csv CSV files containing activity and point measurement data, respectively. You can use any standard CSV tools and libraries to read and modify these files, including loading them into spreadsheets such as the freely available Google Docs (examples below).
GPS tracks are included as GPS eXchange Format (GPX) files, one file for each activity with an associated a track. Please note that the GPX filename corresponding to any given activity is included at the end of that activity’s cardioActivities.csv row, too. You can step through the CSV file until you find an activity of interest, then use the GPX filename field to jump out to that particular activity’s track.
Here’s an abridged example of a GPX file containing GPS track data for the first entry in the example activities from above:
Another thing to note: The export does not include photos that the user might have uploaded during RunKeeper recorded activities. Our team discussed including photos versus not, and decided not to for the following reason: We believe including them would be redundant at best (since those photos also remained on the user’s phone at upload time) and could lead to very large ZIP file size and download time at worst.
Your feedback on any and all aspects of this would be appreciated. You can reach us via:
- A response to my data export post in the Health Graph discussion group
- A message to our Health Graph Twitter (@HealthGraphAPI), Facebook, or Google+ accounts
- If you find something you believe is a bug, or you have a new user data export-related feature you would like to request, please visit our Support site to search for your issue; if it’s not already filed, please consider filing it.
If we’ve missed anything critical, please let us know.
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.
Scosche myTREK: Health Graph wireless pulse monitoring on your forearm
Posted: December 23, 2011 Filed under: Android, API, Apps, Fitness, iOS, Partners, Running | Tags: activities, api, apps, calories, device, fitness, healthgraph, mytrek, partners, partner_profiles, pulse, rickwenner, scosche, wireless Leave a comment »We’ve previously featured Health Graph (@healthgraphapi) applications and third party libraries in our ongoing partner profiles series. This time, we turn our attention to a device partner, Scosche Industries (@scosche), and their Health Graph-integrated myTrek device. Read on to learn more about myTrek and how Scosche is taking advantage of the Health Graph.
Bill Day: Please tell us about yourself and your company.
Rick Wenner: My background is as a fitness educator and I have spent the last decade instructing thousands of fitness professionals and consumers on how to properly maintain a healthy lifestyle. I have always seen technology as a crucial tool in expanding the possibilities and opportunities within the fitness industry. I have dedicated much of my professional career to developing award winning fitness products. I am now the Category Manager for Health and Fitness at Scosche Industries where I focus on promoting and developing Scosche’s line of Health and Fitness products.
BD: What is the “elevator pitch” for why someone should use myTREK?
RW: The Scosche myTREK is a wireless pulse monitor that is worn on your forearm as opposed to a traditional chest strap. Paired with the Scosche myTREK app, you can manage your pulse, training type, calories burned, distance/speed/pace and more. Scosche myTREK also allows you to control your music while you work out with the integrated buttons on the armband; volume up/down, play/pause and previous/next track.

BD: How did you get started using the Health Graph API?
RW: We realized that RunKeeper had a great platform for individuals tracking and sharing their health metrics with like-minded consumers. Once we launched we saw that quite a few of our users wanted to have the ability to share their myTREK workouts on RunKeeper’s Health Graph.
BD: How is using the Health Graph benefiting your business?
RW: Consumers began noticing our team’s posts during our beta testing and started asking how they could link their myTREK to the Health Graph. Since then, we have had great feedback from our existing customers, who were hoping that they would see this partnership. We are also seeing an increase in app downloads and myTREK purchases.
BD: Which portion of the Health Graph API do you use, and why?
RW: We are currently using the Fitness Activities portion of the Health Graph API. We use this to allow users’ myTREK activities to be continually monitored.
BD: What do you like about the Health Graph?
RW: The Health Graph is a great tool for enabling individuals to track their progress in one or more aspects of their fitness journey. This type of constant feedback shows the individual their end result; this can either be rewarding or show them that they need to modify their workouts to see the desired results.
BD: If you could request any new feature from the Health Graph, what would it be? How would you use it?
RW: The Scosche myTREK app allows users to name their workouts. It would be great if the Health Graph could recognize what the user named the workout and track it accordingly. Currently the only way to define the workout is via the notes section.
BD: Can you share any future plans for myTREK and related Scosche products? What’s coming next that your users will be excited about?
RW: Scosche has big plans for the Health and Fitness Category; however, we are not at liberty to divulge them at this time. What I can say is that we will be launching an Android app in the very near future.
BD: Is there anything else we should know about you, Scosche, or myTREK?
RW: We are focused on creating a complete exercise experience; an experience which motivates, guides and entertains by seamlessly incorporating music, social media, and all that connects you to the world. Scosche’s award winning myTREK app and hardware are a glimpse of the great things that are still to come from the Scosche Health and Fitness Category.
Bill Day (@billday) is Platform Evangelist for RunKeeper where he helps developers learn about and use the Health Graph.

















