Suggestions for library/tracks showing completion

Not sure what you want to do with an API exactly but the completion data is already available in JSON, just add .json to the end of your profile.

Here's an example I made a while back http://codepen.io/jamesbarnett/pen/Giakr

Thanks for your reply. That's exactly what I thought about Freelancer when I first heard about their API. Why would they release an API? Of course, exactly what people might do with an API is much greater than the scope of my immediate imagination. It would depend largely on Treehouse and their objectives, I guess. I'm far from an expert. That's why I'm here. I just love this stuff. It's an obsession.

I just believe an API could potentially foster creativity amongst the community here. Say someone wanted to create a unique mobile app that could plug into to the API. There are all kinds of possibilities. Perhaps the social aspects of this platform could be plugged it into other social media or collaborative initiatives like learning-games based on the acquisition of insight into development principles. But like I say, I don't know the full implications of such a thing. I'm sure there are many pitfalls and possible impeding limitations I am unaware of.

I'm curious what features you are looking for in an API?

Let me think about that for a little bit. I'll reply back as soon as I can. I'm having internet issues.

Okay, warning: This message somewhat lengthy.

What I like so far about the community here is how eager people are to learn. Not that I’ve been here long; it’s only been but a few days. But it’s refreshing to see others curious about the various technologies available today. That is an exciting community to be a part of. It reminds me I’m not alone in my struggles to learn as much as one finite lifespan will allow.

Each organization seems to cultivate its own culture. Just like Starbucks and Target and Walmart. Target has a very different kind of atmosphere than Walmart, and Starbucks is completely disparate from Waffle House or iHop. They all attract different types of people.

Take Youtube’s API, for example. Youtube is essentially a social network for personal broadcasting. It’s an exchange for views and expression — be it entertainment, educational, etc.

Their API allows you to query videos, pull metadata, various information about the channels, users and so on. Some of their features require the user to authenticate, while other aspects of the API simply return whatever public information is available for unauthenticated anonymous users.

Hypothetically, if I did not like how Youtube handled alerting me of new videos from channels I am subscribed, I could potentially create my own app that would notify me of any channels flagged as a priority. Facebook is very similar. I could write an app to monitor discussion threads I find intriguing.

Treehouse isn’t much different. It’s still somewhat of a social network. It’s just more specific and refined than the general purpose variety. Unlike other places, people come here with a dedicated mission. They come here with a purpose. It’s definitely much bigger than any one user can discern. And so what’s useful or fun for me might not be for everyone. In any case, I really like the point system here. I enjoy the quizzes and structure of content. The videos here are amongst the most entertaining educational presentations I’ve encountered thus far.

Since TH is a community based around learning technology, it puts them in a unique position to potentially do stuff in ways that has not been done. Example: A lot of newcomers may not even know what an API is yet, let alone what practical (and just plain fun) kind of things can be done with it. But then TH is an educational institution.

Perhaps there is a way to turn an otherwise ordinary API into a more socially driven mechanism for learning. The bedrock for this has already been laid down. You already have a good community. There are quizzes and there is a point system. Just because you release an API doesn’t mean it has to be in the same spirit of other APIs.

What if the API was part of the whole learning process? What if it was an API designed specifically for their students in some type of sandbox-like environment? In other words, set up in such a way to give the community the ability to work with a real API, while not disrupting everyday business for TH. This could encourage participation amongst peers, competition, and collaboration. It would also prepare TH subscribers for tackling more traditional APIs once they learn what can be done without knowing all the gory interworking details.

It’s only my third or fourth day here. In the coming weeks, I am sure I’ll get more ideas as I become more familiar with TH. I will post a more direct answer to your question in a separate thread, entitled “Treehouse API”, once I have more information to base my suggestions on.