Voices: stephenb, jangliss, Hughlander, karell, grkg8tr, busterbenson, LeslieB, cachapa, bookchiq, ashapiro75, KylePJohnson, chmouelb, alexgm, tjablon, tommyjr, infernix, mashdot, spchamp, bendoherty, jghaines, and lucykathrynrobi
|Sep 14, 2009 4:09pm||
DailyBurn’s API Documentation can be found here:
If you have any comments/questions specifically about the API docs, then please feel free to update this topic.
|Nov 5, 2009 7:41am||
Are there any plans on a sandbox of sorts? I’d like to tinker with the API before working on a full blown app. I’m considering a Windows Mobile version, similar to the iPhone app.
|Nov 10, 2009 4:40pm||
We have discussed having a sandbox environment, but currently don’t have time to maintain it. For now I recommend setting up a test user account that you can use for playing around with the API’s functionality on.
|Jan 8, 2010 6:20pm||
Will the workout API but released soon? I’m thinking of an app that just gives a one page summary of the last exercise set associated with each workout. However the only way to do so currently seems to be to almost reverse engineer it by keeping track of the dates we asked for exercise logs and track what workout they were associated with and then from that determine what exercises are in a specific workout.
|Jan 25, 2010 6:29pm||
The workout API may be changing a bit soon. I’d suggest waiting on developing anything specific to workouts and progress submitted towards them. Please do keep us posted on your interest in this section of the API though, we’ll do our best to provide some documentation towards it once we feel it’s in a solid state. Thanks!
|Feb 11, 2010 4:16pm||
Very good stuff on the API folks – perfect or not it is a step in the right direction.
Are there any places where we can track the API development more closely – twitter, codeplex, blog, etc?
Let me know – thanks
|Feb 12, 2010 4:14pm||
Anyone else interested in following API development more closely? The idea of having a twitter account for this makes sense to me, if there are enough followers.
|Feb 12, 2010 5:55pm||
It definitely would help with staying up to date with changes.
|Feb 14, 2010 6:41am||
I’d love to have as many updates as possible, I seem to have missed notifications on replies in this thread, and just signed up to subscribe to the rss feed for the forum itself. RSS is my preferred notification over twitter, but anything would be great.
|Jun 11, 2010 5:29pm||
Hi Stephen, any update to the workout API? I’d like to be able to query custom work outs and create exercise sets based upon them. I see that workout_id is already a parameter to exercise sets both for setting and retrieving, I just need to be able to map a user to their workouts, and workouts to their workout_id.
For testing purposes until that’s up is it ok for me to write some code to reverse engineer a test users workouts? IE: Get the last month’s exercise log by date, for each day there’s data, map what exercises were done to their workout_id, allow user to create new exercises only from that workout associated with the workout_id?
Ideally I’d like to make a small android compatible web page for personal use that will allow me to enter sets/reps/weights.
|Jun 14, 2010 11:11pm||
We’re working on some API changes related to Training Plans and custom workouts at the moment. Until those changes are in production there isn’t really a good way to access just a user’s custom workout routines.
You’re welcome to try the reverse-engineering approach, but I think it will tend to not be bullet-proof. If it’s just for personal usage though, then I bet you could make it work…
|Jun 18, 2010 1:42am||
I’d love to get access to the API but it seems like registration is down at the moment. Am I missing something? How do you get access to the API? I’ve tried some of the URLs that supposedly don’t require authentication and am still getting API Access Denied errors.
Thanks for any help you can offer!
|Jun 18, 2010 4:51am||
Sorry. API registration is temporarily on hold, but the good news is it will be coming back soon (and it will be a self-registration process that any DailyBurn user can do). This will be an improvement over our old email back/forth process, and we’re just tying up some loose ends before launching it.
busterbenson: While some calls do not require user authentication, all API calls require API authorization.
|Jun 20, 2010 10:24pm||
Ah, that makes sense regarding the authorization. Should I keep an eye out on the blog or on Twitter for an announcement about a self-service registration process? I’m anxious to try it out, but have a bit of time before I’ll be able to really dive in.
Thanks again for making this API. I think great things will come of it.
|Jun 27, 2010 11:01pm||
How can I get notified once the API registration is available again? I’m keen to get started on expanding the DailyBurn Platform.
|Jun 28, 2010 3:45pm||
Regarding the API registration, the most sure-fire way is to check back every week or so on the main Docs page. Once it’s available, the links for registering/managing your client applications will show up there.
We’ll also try to remember to post to twitter (possibly blog too), I’ll pass those ideas along.
|Jul 14, 2010 3:34pm||
@StephenB are you also making changes to the Body Log Entries API?
I’ve got basic synchronization to work in my Android app, but it’s impossible to make it work 100% well without a better API.
I guess that would be enough, but I might be forgetting something.
Since I’m typing here… Another thing which has always puzzled me about DailyBurn is why you allow multiple entries per day if the rest of the site (charts, challenges, etc) always assume only one entry per day?
|Jul 15, 2010 5:32pm||
Any ETA on API registration for new developers? Like Leslie, I’m eager to get started and have been checking back every few days, but am starting to despair. :)
|Jul 19, 2010 4:29pm||
So, one thing to mention – we’ve decided to build a v2 version of the API that is coinciding with new projects we’re building internally. All of the changes we’re making on the API will be released in the new v2 version.
@cachapa: I don’t think those particular changes have been made yet. I’ll take note of them and see what we can do.
Aug 2, 2010 3:35pm
Any update about the new registration process and when it will be available? I started as a user but I’m a developer and I actually was a personal trainer for a long a time so I have gathered quite a bit of insight and of course think I could do a better job on the interface… :) So I would like to take a stab at it.
|Aug 2, 2010 9:50pm||
Soon. The changes are made in our master branch, so it’s just waiting for our next deploy :-) Sorry that this has been delayed for so long. We were forced to do a code freeze for weeks while migrating our servers to a new datacenter (still trying to get things back into a rhythm).
|Aug 6, 2010 6:30am||
I just realized my app started crashing due to a change in the <user> object returned. What is the best way of staying up to date with changes to the API? Can there be a mailing list to which registered developers can be added. It would save a lot of time and effort to have a little heads up when changes are coming.
|Aug 9, 2010 11:37pm||
I am having some issues with returns from the API when sending BASIC auth requests. Could use a little support on that issue, however unsure who or how to contact someone.
|Aug 10, 2010 11:06pm||
Kyle: can you start a new topic about this subject in this forum? I don’t want to take this conversation offline in case the solution we come up with is helpful to others.
grkg8tr: Sorry if some changes caused problems. We are now versioning our API so that will help that problem.
|Aug 17, 2010 1:06am||
@grkg8tr i think there is some stuff to update for burnbot to be updated regarding adding some foods as favourites
@StephenB would be feasible to have a RSS feed of the diff of the API documentation, you guys seem to use RoR not that i know anything about it but maybe they have some kind of ‘easyness’ for that.