Posted on 06-16-2014
One of the mutiple requests to review APIs currently in my inbox, is from the camera platform Dropcam. Every email or tweet I get, asking me to review an API, I at least click in to see what is happening, looking for that good story.
Sometimes the API itself, can be good enough to be the “thing” that I tell a story about, but most often it is about a specific approach the API provider takes. Regardless, I look throughr all aspects of an API, sign up for an account, play with endpoints, look through documentation and code, and terms of service—trying to find any angle for a compelling story.
When I clicked into Dropcam's developer area, I can’t sign up for the API, play with endpoints, review documentation and code, but I can look at terms of service! Dropcam asks that you apply to be part of their beta program, before you can look at or play with anything.
Dropcam assures me that their API is RESTful and uses its verbs, with all endpoints using HTTPS, and requests and responses in JSON. Dropcam uses oAuth for authentication and authorization, showing that all the proper technology and security building blocks are in place--thing is I need to see for myself.
I can understand putting an approval layer at the point someone wants to take their application public, but if someone owns a Dropcam, they should be able to signup and start hacking on their device and the supporting cloud infrastructure. With modern API management infrastructure you have the power to control what resources developers have access to, with identify the bad actors, without limiting who has access to learn about your platform.
Most importantly it prevents people like me from just reviewing the endpoints, documentation and the real meat of the Dropcam developer program. I’m not building an application, I just want to write a story about what is possible, and without playing with it I can’t do that. I’m not like many other tech journalists who will take a press release and rewrite it—I want to play!!
So far, that is my review Dropcam. Sorry. ;-(
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- 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