Posted on 10-22-2012
Github is a frequently used service in the toolbox of API owners. The most common use of Github is for publishing API SDKs in a variety of languages and platforms. But when it comes to truly being an "open API", some API owners are actually open sourcing their API design using Github.
Open sourcing the design of your API will not be sensible for every provider. Many companies are looking to ensure developers use their API, maintaining an advantage over competitors. However in some cases, open sourcing the design of your API is a way to ensure interoperability between partners or among mutliple companies within a certain business sector.
Simple examples of an API design might be for common systems like blogs, news, links, calendars or other API designs that don't deliver any sort of proprietary offerings. If you are looking to ensure synchronicity between say, the calendar of multiple organizations, developing a single API and open sourcing the design and possibly a version of it in multiple programming languages, might make sense.
With a consistent API design, and code to deploy the API, any organization can download or fork the Github code, deploy the API for themselves--ensuring consistency and interoperability between any deployment. If a single organizations has unique needs, they can extend and commit the code back to Github, allowing the central repository manager to decide if it is a change that should be added to the core offering.
Not all APIs are created equal. Consider the possibility of actually open sourcing your API, the benefits it might bring to others, as well as your organization--they might exceed keeping it closed and proprietary.
This approach to using Github, is by far the truest meaning of the word, "Open API".
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate