Google Drive API Getting Started: Quickstart Guide (2026)

Getting started overview

Integrating with the Google Drive API enables applications to programmatically manage files and folders stored in Google Drive. This includes operations such as uploading, downloading, searching, and managing sharing permissions. The process typically involves setting up a Google Cloud project, enabling the Drive API, configuring OAuth 2.0 credentials for authentication, and then implementing client-side code to interact with the API endpoints.

The Google Drive API is part of the broader Google Workspace ecosystem, allowing for deep integration with other Google services. It supports various programming languages through client libraries, facilitating development across different environments. Developers are encouraged to review the official Google Drive API v3 documentation for detailed specifications and guides.

Here's a quick reference for the initial setup:

Create an account and get keys

To begin, you need a Google Account and a Google Cloud Project. If you don't have a Google Account, you can create a new Google Account. Once you have an account, navigate to the Google Cloud Console.

1. Create or Select a Project: In the Google Cloud Console, from the project selector dropdown, either create a new project or select an existing one. A project organizes all your Google Cloud resources.
2. Enable the Google Drive API: Use the navigation menu to go to "APIs & Services" > "Library." Search for "Google Drive API" and select it. Click "Enable" to activate the API for your project. This step is crucial for your application to make any calls to the Drive API. For more details on this process, refer to the Google Drive API enabling guide.
3. Configure OAuth Consent Screen: Before creating credentials, you need to configure the OAuth consent screen. This screen is displayed to users when they grant your application access to their Google Drive data. Go to "APIs & Services" > "OAuth consent screen." Choose "External" for public applications or "Internal" for Google Workspace organization-only applications. Fill in the required fields, including application name, user support email, and developer contact information. You will also need to define the scopes your application will request. For file management, common scopes include https://www.googleapis.com/auth/drive.file (for files created or opened by the app) or https://www.googleapis.com/auth/drive (for full access to all files). A comprehensive list of Google Drive API authorization scopes is available in the documentation.
4. Create Credentials: Navigate to "APIs & Services" > "Credentials." Click "Create Credentials" and select "OAuth client ID." Choose the application type that best fits your needs, such as "Web application" for server-side or frontend applications, or "Desktop app" for applications running on a user's machine. Provide a name for your client ID. For web applications, you'll need to specify authorized JavaScript origins and authorized redirect URIs. After creation, you will receive a client ID and client secret. These are essential for your application to authenticate with Google's OAuth 2.0 server. Keep your client secret secure and do not embed it directly into client-side code.

Your first request

Once you have your OAuth 2.0 client ID and secret, you can make your first authenticated request. This often involves using a Google API client library for your preferred programming language. The following example demonstrates how to list files in a user's Google Drive using Python.

First, install the Google Client Library for Python:

pip install --upgrade google-api-python-client google-auth-httplib2 google-auth-oauthlib

Next, use the following Python code snippet. This code will guide the user through the OAuth 2.0 consent flow in their browser, obtain the necessary tokens, and then list the first 10 files in their Drive.

import os

from google.auth.transport.requests import Request
from google.oauth2.credentials import Credentials
from google_auth_oauthlib.flow import InstalledAppFlow
from googleapiclient.discovery import build
from googleapiclient.errors import HttpError

# If modifying these scopes, delete the file token.json.
SCOPES = ["https://www.googleapis.com/auth/drive.metadata.readonly"]

def main():
    """Shows basic usage of the Drive v3 API.
    Prints the names and IDs of the first 10 files the user has access to.
    """
    creds = None
    # The file token.json stores the user's access and refresh tokens, and is
    # created automatically when the authorization flow completes for the first
    # time.
    if os.path.exists("token.json"):
        creds = Credentials.from_authorized_user_file("token.json", SCOPES)
    # If there are no (valid) credentials available, let the user log in.
    if not creds or not creds.valid:
        if creds and creds.expired and creds.refresh_token:
            creds.refresh(Request())
        else:
            flow = InstalledAppFlow.from_client_secrets_file(
                "credentials.json", SCOPES)
            creds = flow.run_local_server(port=0)
        # Save the credentials for the next run
        with open("token.json", "w") as token:
            token.write(creds.to_json())

    try:
        service = build("drive", "v3", credentials=creds)

        # Call the Drive v3 API
        results = service.files().list(
            pageSize=10,
            fields="nextPageToken, files(id, name)").execute()
        items = results.get("files", [])

        if not items:
            print("No files found.")
            return
        print("Files:")
        for item in items:
            print(f"{item['name']} ({item['id']})")

    except HttpError as error:
        # TODO(developer) - Handle errors from drive API.
        print(f"An error occurred: {error}")


if __name__ == "__main__":
    main()

Before running this code:

1. Download your client configuration file. From your Google Cloud Credentials page, click on the name of your OAuth 2.0 client ID, then click the "Download JSON" button.
2. Rename the downloaded file to credentials.json and place it in the same directory as your Python script.
3. When you run the script, a browser window will open, prompting you to log in to your Google Account and grant permission to your application. After authorization, the script will print the names and IDs of up to 10 files from your Google Drive. This process is detailed in the Google Drive API Python Quickstart.

Common next steps

After successfully making your first API call, you can explore more advanced functionalities of the Google Drive API:

• File Management: Implement operations to upload new files, download existing files, update file content, and delete files. The Google Drive API file management guide provides examples for these tasks.
• Folder Management: Create and manage folders to organize files within Drive. This involves creating new folders and moving files between them.
• Sharing and Permissions: Control access to files and folders by setting permissions for specific users or groups. This allows for collaborative features within your application. More information on managing sharing permissions is available.
• Search and Query: Utilize the powerful search capabilities to find files based on various criteria, such as file name, content, type, or modification date. The Google Drive API search files documentation is a good resource.
• Real-time Notifications: Set up change notifications to be alerted when changes occur to files or folders in a user's Drive, enabling real-time synchronization or updates in your application.
• Error Handling: Implement robust error handling to gracefully manage API errors, such as rate limits, authentication failures, or resource not found issues.
• Explore Other SDKs: If Python isn't your primary language, explore the client libraries for Java, Node.js, PHP, Ruby, .NET, or Go to integrate the API into your preferred development environment.

For broader API security best practices, consider reviewing general guidelines for OAuth 2.0 security considerations to ensure your application handles tokens and user data securely.

Troubleshooting the first call

Encountering issues during your first API call is common. Here are some troubleshooting tips:

• "API Not Enabled" Error: Double-check that the Google Drive API is enabled for your project in the Google Cloud API Library.
• Authentication Errors (401/403):
  • Incorrect Credentials: Ensure your credentials.json file (or equivalent for other languages) contains the correct client ID and client secret downloaded from the Google Cloud Console.
  • Invalid Scopes: Verify that the scopes requested by your application match the permissions you configured in the OAuth consent screen and are sufficient for the API calls you are attempting. For example, https://www.googleapis.com/auth/drive.metadata.readonly only allows reading metadata, not file content.
  • Token Expiration: OAuth 2.0 access tokens have a limited lifespan. Ensure your application handles token refreshing using the refresh token. The Python example provided includes logic for this.
  • Redirect URI Mismatch: For web applications, ensure the authorized redirect URIs configured in your OAuth client ID match the URI your application uses to receive the authorization code.
• "User Rate Limit Exceeded" (403): This indicates you've sent too many requests in a short period. Google Drive API has usage limits and quotas. Implement exponential backoff for retries to handle this gracefully.
• "File Not Found" (404): If you're trying to access a specific file, ensure the file ID is correct and the authenticated user has access to that file.
• Missing token.json or credentials.json: If using the provided Python example, confirm that credentials.json is in the same directory as your script and that token.json (generated after the first successful authentication) is not corrupted or missing.
• Check Google Cloud Logs: The Google Cloud Logging service can provide detailed error messages and request details, which can be invaluable for diagnosing issues.
• Community Support: If issues persist, consult the Google Drive API support resources, including Stack Overflow, for community assistance.