YouTube: API key, uploading Shorts and the audit

By the end ClipOnTap loads the views of your videos, shows live streams in the radar and can upload a finished clip to your channel.

20 minYou need: A Google account with a YouTube channel.

1. API key: views and the radar

  1. Create a project. Open console.cloud.google.com and create a new project.
  2. Enable the API. In the API library (APIs & Services → Library), find “YouTube Data API v3” and enable it (Enable).
  3. Create a key. Open Credentials and create an API key. In its restrictions, allow only YouTube Data API v3.
  4. Paste the key into ClipOnTap. ClipOnTap → Connections, field YouTube API key (radar), then “Save settings”. After saving you see only the last four characters.

The key is used by ClipOnTap → Live radar (platform youtube) and by the “Load views from YouTube” button in ClipOnTap → Performance & money. One radar listing costs about 101 of the 10,000 daily quota units.

2. OAuth client: uploading

Uploads run under your own Google project, not a shared one.

  1. Set up the consent screen. In the same project, open the OAuth settings (OAuth consent screen, called “Google Auth Platform” in the newer console). Fill in the app name and email, and set the audience to External.
  2. Add yourself as a tester. Under Audience → Test users, add the Google account that owns your channel.
  3. Create an OAuth client. Under Clients (or Credentials → OAuth client ID), create a client. For the application type, pick the one named on the youtube card in ClipOnTap → Connections; right now that is “Desktop app”.
  4. Download the client file. Google offers a JSON download.
  5. Hand the file to ClipOnTap. In ClipOnTap → Connections, the youtube card. ClipOnTap expects it under the name youtube_client_secret.json. The card switches from “not connected” to “ready to sign in”.
  6. Sign in your channel. Click “Sign in to YouTube”. In the new tab, pick the account with the channel and allow both kinds of access: uploading videos and reading the account (this is how ClipOnTap checks which channel it uploads to). Google warns that the app is not verified. It is your own app, so continue.
  7. Check the card. It should show “connected” and “channel:” with the name of your channel.

You upload one clip at a time: ClipOnTap → Done → “Upload to YouTube”, then confirm the prompt. Visibility is set by the field YouTube visibility (private/unlisted/public); the default is private.

3. Why a video stays private

YouTube locks videos as private when they are uploaded through the API from a project that has not passed Google's audit. The value in the visibility field makes no difference, and in YouTube Studio you usually cannot switch them to public. This applies to every new project, including yours.

  1. Upload by hand until the audit. In ClipOnTap → Done, click “Upload pack”. The title and description are in youtube.txt. Upload the video in YouTube Studio or in the app.
  2. Request an audit. Fill in the YouTube API Services – Audit and Quota Extension Form. Describe what the tool does, that a person approves every upload, that you clip only with permission, that every video links to the streamer, and how many videos you upload per day. Attach screenshots of To review, Done with a caption, and Connections.
  3. Change the visibility after approval. Type public into the visibility field and save.

Troubleshooting

  • “OAuth client missing”. ClipOnTap does not have the client file. Go back to steps 4 and 5.
  • “Google did not allow sign-in: access_denied”. Your account is not among the testers, or you denied access.
  • “sign-in expired or was started again”. Click “Sign in to YouTube” once more and finish it in a single tab.
  • Uploading stopped after a week. While the app is in testing mode at Google, a sign-in lasts 7 days. Click “Sign in again”.
  • “YouTube search: 403” in the radar. The API is not enabled in the project, the key has a different restriction, or the daily quota ran out.
Next guideTwitch: Client ID and Client Secret