Yes, thanks for confirming. Please note that the API docs for DO are -not- correct. This means other DO users will needlessly have difficulty, unless someone can get word to the DO engineers. The API docs need review and correction.
I’m going through the API docs now, and I found a second, different bug in the API docs: The API field “sshkeys” is renamed in v2 API to “sshkey_ids”. This is a known issue from like October 2014, and hasn’t been documented: https://github.com/sckott/analogsea/issues/23
(I have to complain about the docs not being correct… I’ve wasted hours on these two errors, and I haven’t actually got too far into the DO API yet so I expect lots more problems now. My goal is to automate droplet provisioning using scripts, so it’s not like I can ignore the API v2 documentation errors and switch back to the DO web portal. That wouldn’t be automation.
While I prefer to support DO, my time matters… and I may be forced to switch back to Amazon EC2. Through past experience I already know EC2 documentation is up to date and correct.