The API, what is it and what can it do for me?
We’ve been getting that question a lot lately. Though seeming harmless, those questions deal with what the core intent of an API should be: An API’s focus is not really what it does for the Service Provider (though there are some seriously obvious benefits to the Service Provider) but what it does TO the community, the consumers.
A few years ago I jokingly “redefined” the acronym API (Application Programmable Interface) as:
API (Association Producing Interchange): “The interface that a community of developers uses to collaborate, innovate, and build on ideas to change and invigorate a software experience.” We have a unique opportunity as developers; we can come together using our various backgrounds and knowledge to make a really great “something” - but we have to connect with people not just systems.
Let’s ask the questions above differently: This is the API, now what am I going to do with it?
If we have done our jobs, you as a developer should feel empowered right about now or will once you get your keys. So long have we treated software as some sterile, stale, immutable blob of code. I spent a full month on the “Architecture” of the version framework in the REST API to avoid breaking interface contacts with software that will be written against it! It’s was the responsible thing to do, but in a perfect world software would be organic, dynamic, “up-to-date”. What if we had the opportunity, nay, the responsibility and commitment to writing organic software?
Think of it like this - the whole “If it’s not broke why fix it” mentality has it all wrong. That’s like saying “If my software is not being used why add functionality to it or make it useable?” To miss-paraphrase Erwin McManus: If you’re going to break something break it BOLDLY.
We have an opportunity to make really beautiful things with the tools we have been given and we have the desire to do it. If you’re a DEV you know what I am talking about - the excitement when you see your handy work being used or when you write that one line of code that is so cool that you have to leave the confines of your socially constricting cube.
So, this is the API, now what are we going to do with it? Let us know, you’ll only be giving back the the community and who wouldn’t want to do that?
- Programming in F#
July 27, 2010 - NoSQL: HuMONGOus Benefits (Part 2)
July 14, 2010 - Our Scrum Team Structure
July 8, 2010 - SaaS & BI - The History & Future
June 29, 2010 - Getting Started with Android
June 22, 2010
2010
2009
2008
Great post Mr. Floyd. I love the talk about Developers getting out and solving the customers problem instead of just building software and letting it become stale.
In addition, FT is in a way giving back to the community and allowing people to extend functionality that perhaps is unique to their own needs.
That’s our mission: Build the right system, the right way, and deliver it at the right time. Great job to all of the FT Dev’s.
Thank you so much for the new API and the great documentation. I am really excited to start working with it. I may be missing something, but will there ever be the ability to access contacts (specifically add contacts attributed to a specific individual) through the API, and will there be the ability to process Event Registrations?
Brendan:
Our goal is to introduce as many resources into the API as possible. To be a little less vague though: We have had many requests for contributions, groups, events, etc…
If you have a moment share with the community what your plans on consuming the API are, you may find that there are others that share your needs. We are taking those ideas and using them to find the next best resource to introduce into the API.
We would like to be able to get headcount data from the API so we can chart our attendees.