FlowingData Forums » your.flowingdata

yfd developer api?

Started 7 months ago by mimlee / 13 posts

  1. I was wondering if a developer api already exists or is in the works? It would be nice to be able to reuse some of the data being sent to and aggregated by yfd (such as most recently read book for instance).

    If not, I suppose a workaround would be to create another app that acts as a go-between my primary twitter account and yfd so that I could grab relevant data on the way over.

  2. there's no API right now, although i'd love there to be one. it could be a while unfortunately since my research focus is on the frontend right now

  3. by the way, seeing your background on quilted, any YFD input would be great :)

  4. Hey Nathan. Thanks for your response. I'd really like to get an API going because I want to selectively publish some of my YFD data. Are you working with any collaborators on this project? Is there room for development support?

  5. I'm the only one working on YFD right now - although I do like the idea of development support. I haven't had any experience with code collaboration though. Do you have any ideas on how I could get that started?

    FYI on the selective publishing, last week "custom pages" went live that lets you pick and choose what data to show on a single page (or dashboard). You can make your custom pages either public or private.

    For example, here's one of my own public pages for health:

    http://your.flowingdata.com/flowingdata/page/50/

    I clearly need to make this more obvious in the UI

  6. yfd is cool! Would be great to see an api, at least a simple REST api to export all of the data to a known format (json/xml).

    --Amit

  7. thanks, journeyer.

    while there isn't an API (yet), you can however, still download your data as a tab-delimited file from your actions log.

  8. Thanks Nathany. That helps for now.

  9. Hmm if you haven't had much previous experience with code collaboration then opening up your.flowingdata to too much development might be overwhelming. You could consider making the code available through something like github.com (if you have the code under version control using Git) where people can fork the code, make patches, and submit the patches for you to review.

    If there are specific features you are interested in having people develop, it might be good to think about creating a list for people to work on. The Dreamwidth community has done a really good job of making it easy for people to contribute in a directed way (http://wiki.dwscoalition.org/notes/Development), but it's also taken a lot of work to set that up.

    In any case, I'd be interested in seeing if there are ways I could help out.

  10. I'd also potentially be interested in both using the existing codebase and contributing to the development of it. I've had some experience creating dashboards and also writing twitter apps and some apis

  11. @mimlee - thanks. i'm gonna look into this. you've piqued my interest :)

    @gordon - will keep you posted

  12. I'm assuming nothing more has happened with regard to the API as its not your focus.

    I would like to download the tab-delimited file via a script (i.e. rather than logging in and downloading it). The OAuth authentication complicates this slightly. I'm certain there is a way to do it but is there any way to gain access to the datafiles?

  13. +1 on the downloading data via a script.

    Another option would be to make a widget for the public custom pages that displayed more than just the last 10 entries. Then an external script could scrape it and do something with the data.

    But getting the tab-delimited file would be ideal.


Reply

You must log in to post.

About this Topic

Tags