API Shutdown

YouTube Data API v2 shutdown AI-researched

Dependency: YouTube Data API v2

YouTube turned down Data API v2 after a staged retirement plan, with v2 calls later returning HTTP 410 Gone — breaking works and tools that relied on v2 feeds unless migrated to v3.

Affected Artworks

Those that will die Total loss Degraded

Gregory Chatonsky

Sniffs/aggregates YouTube media to generate an 'infinite intimacy movie'. APIs for retrieval stop returning data.

Hello World! or: How I Learned to Stop Listening and Love the Noise Major impact Unknown

Christopher Baker

Uses large pools of online video. If the work depends on API-based retrieval, v2 shutdown breaks ingestion.

Seven video responses to Constant Dullaart's 'youtube as a subject' Major impact Unknown

Ben Coonley

YouTube-era video contexts and embeds. Embed/API behavior changes can break playback or listing.

VVEBCAM Major impact Degraded

Petra Cortright

Originally published on YouTube. Platform policy removals + embed changes can de-list the work.

Fixes & Mitigations

  • Migration: Migrate retrieval to YouTube Data API v3; re-auth and re-budget quotas.
  • Archive: Archive videos and metadata (IDs, titles, descriptions) to avoid total dependence on live platform availability.

YouTube announced v2 retirement and, after April 20, 2015, began returning warning feeds and then HTTP 410 Gone for most v2 calls. Migration to v3 required new auth patterns and quota accounting.

Notes

YouTube-related extinctions combine API shutdowns with platform moderation, geo-restrictions, and embed churn; separating these causes is often a key conservation task.

Links