APIv2 - Is "client_id" obsolete?

July 29, 2014 5.6k views

The title says it all. It isn’t clear from the APIv2 docs if client id is even used. If it is not used, what value should be used for wrapper utilities (e.g. tugboat) which require “client id”?


2 Answers

Tugboat is still using APIv1. So it still uses the “Client ID” and “API Key” Those can be managed on the legacy API page.

In the future, as more apps move over to APIv2, you can use an OAuth2 token instead. Check out this article for more info on that.

by Justin Ellingwood
One of the most exciting features about version 2 of DigitalOcean's API is the inclusion of OAuth authentication. This allows users to grant access to applications to use their account. As a developer, you can request access from your users through a simple web UI which will streamline the process of gaining account authorization. In this guide, we will discuss how to interact with this feature as both a user and developer.

Tugboat uses the V1 API, which requires the Client ID and API Key located here

  • Thanks, but is the api key (marked “Hidden” on here) the same one as the “Personal Access Token” for APIv2? Do I need to create another one?

  • The version one “API Key” and the version two “Personal Access Token” are two separate things. If you lost your previous API Key, you’ll need to regenerate it.

Have another answer? Share your knowledge.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!