Posted on 07-04-2014
I have a lot of ideas while being the API Evangelist. It just comes with the territory. I have an Evernote folder that I publish these ideas to, and some of them, like my Screen Capture API, I actually make a reality.
The other night while writing, Shadow API: Launching An API Before Someone Else Does, I went to add the Nebraska homestead record API idea to my Evernote, and I said, ENOUGH! I need a public place to store these ideas, and while I'm at it, I'll enable others to publish ideas there too.
What better way to allow collaboration around a content store or dataset, than a Github repository plus API. So I launched API Ideas, as an individual API project, on the API Evangelist Network. I allows me to retrieve, and add to a list of API ideas, all stored on Github, using a simple web API.
I’ll be evolving the API over time, you can engage with me on the roadmap, and see stories around the project on the updates page. It is just a start, and I will be adding a lot more bells and whistles, and improve search, as I have time.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections