Youtube API

Estimated reading: 4 minutes

Configure Youtube API

1. Log in to Google Developers Console.

To access the Google Developers Console, simply log in using your Google account. If you don’t have one yet, you’ll need to create one before proceeding

Follow this guide to create a new project.

After you’ve created a project, all subsequent actions you take will apply exclusively to that project, including creating the API key. If you’re working on multiple projects simultaneously, be sure to double-check that you’ve selected the correct project by verifying that it’s listed in the top navigation bar.

2. On the new project dashboard, click Explore & Enable APIs

After creating a project, you’ll be taken to a brand new dashboard with different cards: Project Info, Resources, and so on.

Navigate to the APIs & Services and click on Library

3. YouTube Data API v3

After arriving at the library, you’ll find a page that’s been sectioned off. Locate the section labelled “YouTube” and choose the option for “YouTube Data API v3.

Alternatively, you can search for the YouTube Data API on the search bar

4. Enable the API

Once you’ve reached the YouTube Data API page, simply click on the blue “Enable” button to proceed

5. Create a credential

After clicking Enable, you’ll be taken to an overview page

Click Create Credentials.

or you will see a screen will appear with the API key if you did this guide for Google Login

6. OAuth consent screen

on the left side select OAuth consent screen / Click PUBLISH APP to get the next steps

Prepare for verification

You need to complete the requirements below:

An official link to your app’s Privacy Policy
A YouTube video showing how you plan to use the Google user data you get from scopes
A written explanation telling Google why you need access to sensitive and/or restricted user data
All your domains verified in Google Search Console

1. Verification Status

2. Fill the form

Complete the form and click SAVE AND CONTINUE

3. Add or remove scopes

Scopes express the permissions you request users to authorize for your app and allow your project to access specific types of private user data from their Google Account. Learn more

4. Update selected scopes

Search this link in the Update selected scopes:

https://www.googleapis.com/auth/youtube

Select it and Update

5. Your sensitive scopes

Because you added sensitive scopes, which grant access to private Google User Data, you will need to submit your app for verification.

6. How will the scopes be used?

Explain to Google why you need these scopes, how you will use them, and why more limited scopes aren’t sufficient.

Enter this content for Scopes justification

Our website using this permission to can add our youtube channel and then post to video to our youtube channel:
My app will use https://www.googleapis.com/auth/youtube to manage my YouTube account to help our post video and live stream video to my channel

7. Demo video: how will the scopes will be used?

Your YouTube video should demonstrate the OAuth grant process by users and explain, in detail, how you’ll use sensitive and restricted scopes within the app’s functionality for each OAuth client belonging to the project.

You need to record a video like this and upload it to your Youtube channel. Pasting its link to YouTube Link above.

If you don’t see this video please subscribe to Stackposts Youtube to watch private videos for members only

8. Optional info

You can speed up the verification process by providing Google reviewers with more, helpful details about your app.

Enter this content for “Share any final details about your app. Include any information that will help us with verification, like the Project IDs of any other projects that use OAuth.”

This is a video demo for permission above use on our system: [Link Youtube For Recorded Video Test]

9. Final review

Check all information and click SUBMIT FOR VERIFICATION

10. Verification Status

The Trust and Safety team has received your form. They will reach out to you via your contact email if needed. The review process can take up to 4-6 weeks. Expect the first email from our Trust and Safety team within 3-5 days.

You Know Stackposts?