Our Open API Debate doesn't officially start until Friday but our panelists are already getting into it over email. One point they're nailing down is what are APIs and who is meant to use them. You can read some of their points below, but to kick this off I want to share with you an example of what can be done with open APIs.

Steve Wright from Salesforce gave this example as one way that open APIs led to the creation of a new entity, well a mash-up really. It's one many of you might be familiar with - HousingMaps.com. It's a mash-up of Google Maps and Craig's List that plots apartments for rent onto a map. It's really a handy application (it's helped me find an apartment) and was possible because the APIs of Google Maps and Craig's List were available.

Read what our panelists are saying.

Steve Wright from Salesforce gives his explanation of APIs:

"An API is NOT the source code and it's purpose is to create a set of calling routines or a library that can be used to integrate an application with the parent application that is unknown to the parent application."

Another point that Steve made and that was echoed by others is being contended. Steve said,

"An API is not provided for the end users. An API is provided for a new type of value-add partner, essentially an ad hoc partner. And, yes, sometimes this ad hoc partner is also an end user."

But Peter Campbell at Goodwill disagrees,

"I'm an end user who makes use of API's to do things internally that would not be marketable to the broader community, such as set up integration between Salesforce and our client management system. And I regularly negotiate software purchases based on the agreement that I will get the API documentation with the program. While your product offers a great example of how a good API can inspire a community of developers to enhance and stretch the use of a product, and my org definitely benefits from that, internal use of APIs does occur regularly and is not in conflict with public development."

Tom Krackeler from GetActive sees both sides and said,

"APIs are not intended for the donors/activists/members "end users", but for the organization itself or third parties on behalf of the organization to use so that the organization's data is not silo'ed in a single place. And I think there are lots of ways to get the data into and out of systems, of which APIs are one very important way."

I'll post more of our panelists' initial discussion on open APIs and why they matter for nonprofits over the next few days.

And don't forget to listen in the live debate this Friday, October 20, at 10:00 am Pacific. More information is available here.