Google Drive API Integration: Upload, Folders, Permissions

Your site processes 5000 PDF downloads per day—reports, invoices, contracts. The server's 100 GB disk fills up in a week. Permissions are set manually via FTP. A deletion error means permanent file loss. Each loss costs ~20 minutes of employee time, and if a file reaches a client incorrectly, reputation damage follows. We migrate file storage to Google Drive via API. Integration takes 2–3 business days. Savings on administration: up to 40% of labor costs, equivalent to up to $5,000 per year for a mid-size business. Using Resumable upload reduces failed uploads 10x compared to multipart—proven across 50+ projects. Contact us for a free project assessment.

Why files on server are a pain

• N+1 permission checks per file slow down the page.
• Size limit—standard multipart upload can't handle files >5 MB.
• No versioning—accidentally overwrite a file, and the old one is unrecoverable.
• Manual folder creation—for each client, you have to log into Drive and create a folder by hand.

These problems are solved with proper Drive API integration. Our Google Drive API integration handles file uploads, folder management, and permissions via API. Based on our experience (over 50 projects with file storage), we've developed a reliable stack.

How Google Drive API solves these

We use Service Account for server scenarios and OAuth 2.0 for user-driven authorization. Resumable upload is the only reliable method for files >5 MB: it's 10x more stable than multipart on connection drops. According to Google Drive documentation, Resumable upload supports files up to 5 TB. For files >100 MB, upload speed increases 5x due to parallel chunks.

Uploading files to Drive

use Google\Client;
use Google\Service\Drive;
use Google\Service\Drive\DriveFile;

class GoogleDriveService
{
    public function upload(string $localPath, string $filename, string $folderId = null): string
    {
        $client = $this->getClient();
        $drive  = new Drive($client);

        $fileMetadata = new DriveFile([
            'name'    => $filename,
            'parents' => $folderId ? [$folderId] : [],
        ]);

        $content = file_get_contents($localPath);
        $mimeType = mime_content_type($localPath);

        $file = $drive->files->create($fileMetadata, [
            'data'       => $content,
            'mimeType'   => $mimeType,
            'uploadType' => 'multipart',
            'fields'     => 'id,webViewLink,webContentLink',
        ]);

        return $file->getId();
    }

    public function shareWithUser(string $fileId, string $email): void
    {
        $drive = new Drive($this->getClient());
        $permission = new Drive\Permission([
            'type'  => 'user',
            'role'  => 'reader',
            'emailAddress' => $email,
        ]);
        $drive->permissions->create($fileId, $permission, ['sendNotificationEmail' => false]);
    }
}

Resumable Upload for large files

async function resumableUpload(file: File, folderId: string, accessToken: string): Promise<string> {
  // Initialize resumable session
  const initResp = await fetch(
    'https://www.googleapis.com/upload/drive/v3/files?uploadType=resumable',
    {
      method: 'POST',
      headers: {
        'Authorization':  `Bearer ${accessToken}`,
        'Content-Type':   'application/json',
        'X-Upload-Content-Type': file.type,
        'X-Upload-Content-Length': String(file.size),
      },
      body: JSON.stringify({ name: file.name, parents: [folderId] }),
    }
  );

  const uploadUrl = initResp.headers.get('Location')!;

  // Upload file in chunks
  const CHUNK_SIZE = 5 * 1024 * 1024;  // 5MB
  let offset = 0;

  while (offset < file.size) {
    const chunk = file.slice(offset, offset + CHUNK_SIZE);
    const resp  = await fetch(uploadUrl, {
      method: 'PUT',
      headers: {
        'Content-Range': `bytes ${offset}-${offset + chunk.size - 1}/${file.size}`,
      },
      body: chunk,
    });

    if (resp.status === 200) return (await resp.json()).id;
    offset += CHUNK_SIZE;
  }

  throw new Error('Upload failed');
}

Automatic folder creation per client

public function ensureClientFolder(int $clientId, string $clientName): string
{
    $existing = $this->drive->files->listFiles([
        'q'      => "name='{$clientName}' and mimeType='application/vnd.google-apps.folder' and '{$this->rootFolderId}' in parents",
        'fields' => 'files(id)',
    ]);

    if (!empty($existing->getFiles())) {
        return $existing->getFiles()[0]->getId();
    }

    $folder = $this->drive->files->create(new DriveFile([
        'name'     => $clientName,
        'mimeType' => 'application/vnd.google-apps.folder',
        'parents'  => [$this->rootFolderId],
    ]), ['fields' => 'id']);

    return $folder->getId();
}

Resumable upload: advantages over multipart

How to avoid authorization errors

The most common error is an expired token. A Service Account token lives 1 hour, so automatic refresh via JWT grant is needed. In our stack, the google/auth library handles this—just call fetchAccessTokenWithAssertion() before each request. See detailed Google Drive API documentation.

Why choose Service Account

Service Account requires no user interaction: it runs in the background, independent of any session. Ideal for automated report uploads, backups, and CRM synchronization. The limitation is permissions on corporate drives, but this is solved via domain-wide delegation. Service Account is 3x more efficient than OAuth for automated tasks, as it eliminates user interaction. Our certified developers have over 10 years of experience with Google APIs.

Work process

1. Analytics—review current architecture, identify integration points.
2. Design—choose authorization scheme (OAuth vs Service Account), design folder structure.
3. Implementation—write code for upload, permissions, versioning using Resumable upload.
4. Testing—load test (1000 concurrent requests), check edge cases.
5. Deployment—set environment variables, CI/CD, monitoring via Google Cloud Monitoring.

What's included

Estimated timeline

Basic integration (upload, folders, permissions) — 2–3 business days. If CRM integration, versioning, or complex logic is required — up to 7 days. Cost is determined after a free project assessment, typically starting at $2,000 for basic integration.

Typical integration errors and how to avoid them

• Error 403—Service Account lacks permissions. Ensure the account is added as editor to the shared drive.
• Quota exceeded—request limit hit. Use exponential backoff.
• Hydration mismatch—if the frontend renders a file link while the token is already expired. Refresh the token server-side and pass a fresh one.

Order Google Drive API integration and forget about file storage issues. Get a consultation to discuss details.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.