Posted on 05-30-2012
I see the term "open API" used a lot out there in the API space. I feel there are truly very few actual open APIs, but the term has been co-opted by the media, many API owners as well as API service providers.
The only two open APIs I can think of, off the top of my head are:
I’m sure there are more, but will have to do some more research to identify them.
So what makes an open API?
- Publicly Accessible
- Open / Self-Service Access
- Read and Write Capabilities
- Data Openly Licensed
- Interface Openly Licensed
Those seem like a few of the obvious ones, what else am I missing? Many companies are actively using the term "open API", when they should be using the term "public API".
I think many companies could easily make the choice to truly be open, but choose to just use it as a marketing term, rather than in a literal sense.
Let's call APIs what they are really are, "public APIs".
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- Hipster Coffee Shop Interface
- Separating The Layers Of The API Operations Onion While Thinking About API Copyright
- Implementation Of An API Design Should Never Require Permission From The API Designer
- What Would API Copyright Have Done To The Birth Of Cloud Computing
- The Machine Readable Questions We Should Ask Of Terms Of Service
- Retrieve My Data Like Retrieving Video Surveillance Photos From CCTV
- Restaurant Menus As Analogy For API Copyright
- The Future Of Public Private Sector Partnerships Being Negotiated At The API oAuth Scope Level
- One Of The Problems With API Terms of Service Is That There Is No Negotiation