What Would a Stack Overflow API Look Like?
We are now gearing up to build the first official Stack Overflow API.
Please bear in mind that the first version of the API will be read-only by design. We’d rather attack the much harder problem of writing (that is, submitting questions, answers, and comments) in V2 with improvements rolled in from our experience having the read-only V1 API out there first.
To get an idea of what working with this imaginary Stack Overflow API could look like, browse the project Stack Overflow user Kevin Montrose set up:
Stack Exchange API on Google Code
- Documentation for the current Stack Overflow “API” it uses (warning: bad, incomplete, broken, unsupported)
To be 100% clear, we are NOT blessing this as an official API, but we’d like to take advantage of the hard work Kevin has rolled into his code to help produce a proper Stack Overflow API that doesn’t suck.
Because what currently passes for an API on Stack Overflow was never truly intended as such, it’s important to regard what’s in place now as a preliminary sketch, a temporary crutch, a placeholder for something better.
To produce a decent read-only V1 API for Stack Overflow, we need your input:
Read through the highest voted questions tagged [api] on meta.
- Browse Kevin’s document Desired Stack Overflow API which is based on his experience writing SXAPI.
Now, what do you want to build that uses the API? The perfect API for this task, called from your preferred programming language, would do … what, exactly? What’s clean? What’s simple? What’s supportable and scalable?
If WordPress comments are too limiting, and you’d like to post some code samples or use Markdown formatting, feel free to use the SXAPI Meta question to do so — or any place on Meta, really, as long as it’s properly tagged with [api].