Google Drive · Authentication Profile

Google Drive Authentication

Authentication

Authentication profile for the Google Drive API v3. The captured OpenAPI does not declare securitySchemes, so this profile was upgraded from Google's Drive auth documentation. All Drive API requests require an OAuth 2.0 access token (three-legged for user data; two-legged service-account / domain-wide delegation for Workspace). API keys authenticate only fully public file reads. Scope detail lives in scopes/google-drive-scopes.yml.

Google Drive secures its APIs with oauth2 and apiKey across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, deviceCode, and jwt-bearer flow(s).

Cloud StorageCollaborationDocument-ManagementDrivesFileGoogleStorage
Methods: oauth2, apiKey Schemes: 2 OAuth flows: authorizationCode, deviceCode, jwt-bearer API key in: query

Security Schemes

OAuth2 oauth2
· flows: authorizationCode, deviceCode, serviceAccount
key apiKey
· in: query ()

Source

Authentication Profile

Raw ↑
generated: '2026-06-20'
method: searched
source: openapi/google-drive-openapi.yml
docs: https://developers.google.com/workspace/drive/api/guides/about-auth
description: >-
  Authentication profile for the Google Drive API v3. The captured OpenAPI does
  not declare securitySchemes, so this profile was upgraded from Google's Drive
  auth documentation. All Drive API requests require an OAuth 2.0 access token
  (three-legged for user data; two-legged service-account / domain-wide delegation
  for Workspace). API keys authenticate only fully public file reads. Scope detail
  lives in scopes/google-drive-scopes.yml.
summary:
  types: [oauth2, apiKey]
  api_key_in: [query]
  oauth2_flows: [authorizationCode, deviceCode, jwt-bearer]
schemes:
  - name: OAuth2
    type: oauth2
    sources: [docs]
    flows:
      - flow: authorizationCode
        authorizationUrl: https://accounts.google.com/o/oauth2/v2/auth
        tokenUrl: https://oauth2.googleapis.com/token
        refresh: true
      - flow: deviceCode
        deviceAuthorizationUrl: https://oauth2.googleapis.com/device/code
        tokenUrl: https://oauth2.googleapis.com/token
      - flow: serviceAccount
        description: >-
          JWT-bearer (RFC 7523) service-account flow, optionally with Workspace
          domain-wide delegation to impersonate users.
        tokenUrl: https://oauth2.googleapis.com/token
    revocation: https://oauth2.googleapis.com/revoke
    discovery: well-known/google-drive-openid-configuration.json
  - name: ApiKey
    type: apiKey
    in: query
    name: key
    sources: [docs]
    note: Authenticates access to publicly shared files only; cannot access private user data.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/google-drive-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.