Video uploads and metadata handled through the platform API instead of manual studio sessions: a finished render uploaded resumably, full-snippet titles, descriptions, tags and chapters set or updated, and a status endpoint that names a missing credential rather than failing at publish time. The boundary is stated up front: upload, metadata, chapters, captions and thumbnails are automated, cutting and end screens stay manual.
What ports as-is
- The installed-app refresh-token minting script owning the whole loopback exchange
- Raw-HTTP resumable upload
- Full-snippet metadata updates
- A mock-first contract so the feature is built and verified before any credential exists
- The expensive caveats encoded rather than rediscovered (unaudited projects forcing private uploads, a video id never receiving a new file, omitted mutable properties being deleted, chapter format rules, daily quota against per-insert cost)
What we build for you
- Their cloud project and its audit status
- The channel credential and refresh token
- The metadata and chapter template
- The release cadence and who approves a publish
