New Digital Ocean API Enters Public Beta, Improves on Original

Mist.io, a service that allows one to manage and monitor their virtual machines, recently adopted and reviewed the new Digital Ocean API v2 beta release. Having overviewed and exercised the API parameters, new additions and procedures found in v2 seem to be an overall great improvement compared to v1. 

Due to their low prices, high performance computing, and simple interface, Digital Ocean has been a popular choice when it comes to cloud computing and server options. Their new API, currently in beta version, attempts to solve some problems that were encountered in v1. For example, the new implementation tackles issues within v1's keychain management. The old version relied on three nearly identical GET requests for listing, creating, and erasing all keys, whereas the new, truly RESTful interface has GET, POST, & PUT methods with better documented responses. In doing so, the new version solves the lack of information returned when creating SSH keys, a pesky problem developers may have encountered in v1.

Coming well-documented, and improved with added oAuth and IPv6 support, the v2 API is already being consumed and endorsed for use by Mist.io. Digital Ocean is currently hosting an open tracker where developers can pinpoint any problems or bugs with the new service.

Original Article

First look at Digital Ocean’s new API

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at bill@doerrfeld.io. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.

Comments