naxpros.blogg.se - Google drive download activity

For details, see the Google Developers Site Policies. They are available for a variety of programming languages check the page with libraries and samples for more details.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. Tip: The Google APIs client libraries can handle some of the authorization process for you. Information that Google supplies when you register your application (such as the client ID and the To request access using OAuth 2.0, your application needs the scope information, as well as Grants the ability to query the Drive Activity API. Here's the OAuth 2.0 scope information for the Google Drive Activity API: Scope

For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation. Some flows include additional steps, such as using refresh tokens to acquire new access tokens.

If Google determines that your request and the token are valid, it returns the requested data.

Your application requests user data, attaching the access token to the request.

If the user approves, then Google gives your application a short-lived access token.

Google displays a consent screen to the user, asking them to authorize your application to request some of their data.

When your application needs access to user data, it asks Google for a particular scope of access.

(If the API isn't listed in the API Console, then skip this step.)

Activate the Google Drive Activity API in the Google API Console.

Google then provides information you'll need later, such as a client ID and a

When you create your application, you register it using the Google API Console.

The following general process applies to all application types: The details of the authorization process, or "flow," for OAuth 2.0 vary somewhat depending on what kind of application you're writing. Authorizing requests with OAuth 2.0Īll requests to the Google Drive Activity API must be authorized by an authenticated user.

If your application uses Google Sign-In, some aspects of authorization are handled for you. No other authorization protocols are supported. Your application must use OAuth 2.0 to authorize requests. The token also identifies your application to Google. Every request your application sends to the Google Drive Activity API must include an authorization token.