NodeJS脚本调用YouTube API Thumbnail set接口报403 Forbidden求助

Let’s break down what we know first: your Node.js script ran reliably for 3-4 months, then suddenly started throwing 403 errors on the thumbnails.set endpoint starting December 9, 2020. Other YouTube API calls (like liveStreams.insert, liveBroadcasts.insert, and liveBroadcasts.bind) still work fine with the same OAuth credentials, and you’ve already tried updating the Google Data API package and regenerating OAuth tokens with the correct scopes.

Here are the most actionable fixes to try, based on common YouTube API edge cases and policy changes around that timeframe:

1. Double-Check Thumbnail File Compliance #

YouTube has strict, sometimes unspoken, rules for thumbnails that can trigger a "forbidden" error even if your permissions look correct:

• Ensure your image meets resolution requirements: minimum 1280x720 pixels, recommended 1920x1080
• Keep file size under 2MB
• Verify the image doesn’t violate YouTube’s content policies (e.g., copyrighted material, inappropriate content) — automated policy scans were updated around late 2020, so content that worked before might now be flagged

2. Validate OAuth Scope Implementation #

While your scopes (https://www.googleapis.com/auth/youtube, https://www.googleapis.com/auth/youtube.force-ssl, https://www.googleapis.com/auth/youtube.upload) should cover thumbnail operations, try re-authenticating with just the full youtube scope temporarily. Sometimes combining scopes can lead to unexpected permission overlays, especially if there was a backend change to scope validation around that time.

3. Check Live Broadcast Status Restrictions #

The thumbnails.set endpoint has different permissions based on the broadcast’s status:

• If the live stream is already active, some accounts face restrictions on modifying thumbnails mid-stream (even if this worked before)
• Test with a brand new, unstarted live broadcast to rule out status-related blocks

4. Review Account-Level Policy Changes #

Late 2020 saw YouTube roll out updates to creator account policies:

• Check YouTube Studio > Settings > Channel > Status and Features to ensure your account has no active restrictions
• Confirm your account is in good standing (no strikes or community guideline violations) — even a minor recent violation could restrict specific API operations

5. Debug Request Details & Fix Minor Code Issues #

Add verbose logging to capture full error context, and fix a subtle casing issue in your media parameter:

try {
  var thumbnailResponse = await service.thumbnails.set({
    auth: auth,
    videoId: liveVideoId,
    media: {
      body: fs.createReadStream(languageConfiguration.thumbnailPath),
      mimeType: 'image/jpeg' // Corrected lowercase 'm' (JavaScript is case-sensitive)
    },
    requestBody: {}
  });
} catch (thumbnailError) {
  console.log('Full error breakdown:', JSON.stringify(thumbnailError, null, 2));
}

Incorrect casing for mimeType can sometimes trigger unexpected validation errors, even if the error message doesn’t explicitly mention it.

6. Test with the YouTube API Explorer #

Use the official YouTube API Explorer to manually send a thumbnails.set request with your OAuth credentials. This will help isolate if the issue is with your code, or if it’s an account/backend problem:

• If the Explorer also returns 403, the issue is definitely account or policy-related
• If it works, there’s a subtle formatting issue in your script’s request that needs fixing

内容的提问来源于stack exchange，提问作者user9156868