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
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API