Checking out the recently opened infochimps API reminded me of an issue that has been on my research backburner, but also on my radar for a while. Here’s the question: given the proliferating number of web app APIs available to developers, would it be useful to build a search service that helps people find / explore available APIs? I think it would.
Maybe such a thing already exists; trying to find it with a web search along the lines of api search is unhelpful for obvious reasons. I’d be curious if any readers could offer pointers.
What I’m envisioning is a service that supports some hybrid of search and browsing with the aim of helping developers find APIs that provide access to data, functions, etc. that will help in completing a particular task.
For instance, I’m working on a system that helps people manage the searches they perform over time, across systems, on various devices, etc. My feeling is that peoples’ experience with IR systems creates information that is often lost. Some previous research of course addresses this issue… but that is for another post.
This is a pretty nebulous idea, and it’s not obvious to me what data and services are available to support its development.
I’d like to have access to a system that helps me explore:
- data sets exposed via publicly available APIs.
- APIs or API functions x,y, and z that are similar to some API function a.
- restrictions / terms of service for possibly useful APIs (e.g. rate limits, attribution, re-ranking of search results).
- API documentation.
- Libraries available for working with APIs.
Aside from the practical value of such a system, I think API retrieval raises interesting research questions and problem areas. For instance, what kinds of queries (or for that matter what kinds of information needs) can we expect to deal with in this arena? What factors make a particular unit of retrieval relevant? What features of these units offer traction in pursuit of retrieval? What kind of crawling / data acquisition steps do we need to address to move this agenda forward?
I suspect that addressing these problems is as much an HCI problem as it is a core IR issue. Presenting germane information about APIs in a consistent fashion that allows for comparison and coherent exploration strikes me as a tall challenge.