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
- 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
- Which API Do I Need?
- The Expanding API Conference Landscape
- Ocotoparts Open Source Google Spreadsheet
- Andrew Nacin Of WordPress @APIStrat Chicago
- Push Button API Deployment With The Heroku Button
- WordPress Style API Modules For Government
- The Heroku HTTP API Design Guide
- What I Have Been Calling API Trends, Are Slowly Being Baked Into API Operations
- FDA Finding Their API Mojo With A New Drug Label API
- Adding PokitDok To Healthcare Research And The API Stack (Well They Did)
- Why I Am Continuing To Integrate Zapier In My Business Workflow
- Who Is Going To Build The Uber API Platform For The Sharing Economy?
- The API Focused Dev Shop
- Route SMS Messages To Google Spreadsheets Via Twilio API With TwilioSheet
- Publishing Your APIs To Product Hunt
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio