YouTube Data API for Website: Videos, Stats, Caching & GDPR

Automatic YouTube Video Display with Caching and GDPR

A Laravel website often requires automatically showing the latest videos from a YouTube channel. Manual updating takes time and leads to missed new uploads. The standard iframe lacks flexibility: you can't display statistics or customize the preview. We implement YouTube Data API v3: data updates automatically, the quota is not exceeded thanks to caching, and the player complies with GDPR requirements.

What technical problems do we solve?

The first is outdated content. You have to manually change the code every time a new video is released. Our solution fetches the latest videos once an hour and displays a fresh list without your involvement. This saves up to 80% of content maintenance time.

The second is API quota exceedance. Without caching, every page view generates a request to Google. With 10,000 visitors per day, the limit is exhausted in a few hours. Caching in Redis with a TTL of 3600 seconds reduces the number of requests by 100 times — from 10,000 to about 24 per day. In practice, this means zero risk of hitting the limit even with sudden traffic spikes.

The third is GDPR. A standard iframe with youtube.com sets trackers before playback. Using youtube-nocookie.com, we guarantee that cookies are not set until a click. Optionally, we implement a two-step loading: first preview, then player. This fully complies with GDPR requirements.

How does caching prevent YouTube API quota exceedance?

YouTube Data API v3 quota is 10,000 units per day. Without caching, each page visit consumes 1 unit. With 10,000 unique visitors per day, the quota runs out in hours. Caching in Redis with a 1-hour TTL reduces requests to 24 per day — 400 times less. This not only saves quota but also speeds up page load: data is served from memory in milliseconds.

Why is youtube-nocookie.com mandatory for GDPR?

www.youtube.com in an iframe loads trackers before the user presses Play. This violates GDPR. youtube-nocookie.com defers cookie placement until the first interaction. We always embed the player this way:

<iframe
  src="https://www.youtube-nocookie.com/embed/VIDEO_ID?rel=0&modestbranding=1"
  frameborder="0"
  allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture"
  allowfullscreen
  loading="lazy" title="Embedded content from youtube-nocookie.com">
</iframe>

How we do it

Stack: Laravel 11 (PHP 8.3+), Redis for cache, optionally Meilisearch for video search. Example of getting the uploads playlist ID and video list:

$apiKey    = config('services.youtube.api_key');
$channelId = 'UCxxxxxx';

// Get the channel's uploads playlist ID
$channelResp = Http::get('https://www.googleapis.com/youtube/v3/channels', [
    'part'   => 'contentDetails',
    'id'     => $channelId,
    'key'    => $apiKey,
])->json();

$uploadsPlaylistId = $channelResp['items'][0]['contentDetails']['relatedPlaylists']['uploads'];

// Get the video list
$videosResp = Http::get('https://www.googleapis.com/youtube/v3/playlistItems', [
    'part'       => 'snippet,contentDetails',
    'playlistId' => $uploadsPlaylistId,
    'maxResults' => 12,
    'key'        => $apiKey,
])->json();

$videos = array_map(fn($item) => [
    'id'          => $item['contentDetails']['videoId'],
    'title'       => $item['snippet']['title'],
    'description' => $item['snippet']['description'],
    'thumbnail'   => $item['snippet']['thumbnails']['high']['url'],
    'published'   => $item['snippet']['publishedAt'],
    'embed_url'   => "https://www.youtube.com/embed/{$item['contentDetails']['videoId']}",
], $videosResp['items']);

Caching is key. We use Cache::remember:

$videos = Cache::remember('youtube_videos', 3600, function () use (...) {
    // ... API request
});

Comparison of embedding methods: iframe vs API

Comparison: with caching vs without

Integration process

1. Analysis — determine what data is needed: latest videos, statistics, playlists, search.
2. Design — caching scheme (Redis/Meilisearch), request architecture.
3. Implementation — writing code, integration with YouTube Data API v3, cache setup.
4. Testing — quota check, content update, data correctness, GDPR compliance.
5. Deployment — server setup (Docker, Nginx, SSL certificate).
6. Documentation — hand over access, configuration description, cache change instructions.
7. Training — show how to manage channel list and settings.

Timeline — from 1 day for a simple video list to 3 days for a full integration with statistics and search. Cost is calculated individually based on complexity. Get a consultation: contact us and we will prepare an estimate for your project.

Why is this beneficial?

Caching in Redis reduces API requests by 100 times — more effective than storing data in a file or session. Using youtube-nocookie.com avoids regulator complaints. We work under contract, guarantee stability: if the cache fails to update, we fix it within an hour. Over 30 integrations for media and EdTech projects confirm reliability.

Contact us to discuss details and order integration so your website always shows up-to-date videos without manual effort.

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.