Question

APIv2 - Is "client_id" obsolete?

Posted July 29, 2014 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”?

THanks,
-T

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
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

Submit an Answer