apix | Comprehensive restfull api service with php | REST library

Yeah your code may be from google but you have renamed something.

All your calls need to go though the YouTube serivce object

Several possible solutions

declare it as lazy

There are lots of parameters in the API v3 Docs for Search that you can play around with, some in particular you might find helpful are:

• location
• locationRadius
• regionCode
• relevanceLanguage

and you'll need to set type = "channel" to return only channels.

The only mandatory parameter is part which is what data you want returned from your results. For this search call, you only have one option for part, which is "snippet".

This is the only way to do it simply within your multiple parameters, and it will take 100 quota per search, assuming you have an API key already.

If you press 'Try This API' on the right, it'll even give you code snippets you can copy in a variety of languages, since you didn't specify one in the prompt.

Depending on the language, a call could look like the following:

You have to acknowledge that by this code of yours:

You might have enabled domain-wide delegation for your service account, but you are not using it to impersonate a regular user.

The purpose of domain-wide delegation is for the service account to act on behalf of any user in the domain, but in order to do that, you have to specify which user you want the service account to impersonate.

Otherwise, the service account will access its own resources (its Contacts, its Drive, its Calendar, etc.) not the resources of a regular account. Therefore, you'll not see the created contacts if you access Contacts UI with a regular account, since contacts were not created for this account.

You need to impersonate the account for which you want to create contacts.

In order to do that, since you're using Node's getClient(), you should specify the email address of the account you want to impersonate, as shown here:

Not sure if this is the best practice, but what works for us is that we index URL as a separate field only for the API:

Question no. 1:

[...] is it safe not to send request for playsListID and mutate channelId into playsListID by changing first "UC" to "UU"?

Indeed your observation is true. In my experience using the API, I never came across a channel ID that would not be related to its its corresponding uploads playlist ID by:

s/^UC([0-9a-zA-Z_-]{22})$/UU\1/.

But this fact is of an observational nature only, because the API does not document as such the relation stated above. That means that, even if the relation above holds true today, it may well be that (upon an API implementation change) tomorrow it'll be false.

A compromise towards the simplicity of obtaining an uploads playlist ID from a given channel ID by the s///-relation above would be the following: query the Channels.list endpoint for to obtain the uploads playlist ID of a given channel only once and store that association forever.

The query once, store forever statement is correct in the light of the answer to your second question.

Question no.2:

[...] can I be sure, that channelId and uploads playlist id are constant for channel?

Yes, you can be 100% sure that once a channel was created and until the YouTube site and its API exist, the ID of that channel and the ID of the uploads playlist of that channel will not change. The IDs of channels that cease to exist are not reused for to identify newly created channels.

You have to acknowledge that invoking the Channels.list API endpoint, by passing to it the parameter forUsername, is by no means the same thing as going to the YouTube's Web UI for to apply a manual search. For these things to come to light, do bear with me for a little while...

According to the official docs, the Channels.list endpoint invoked with forUsername=... produces the meta-data associated to the channel of which username is given as argument to the parameter forUsername:

forUsername (string)

The forUsername parameter specifies a YouTube username, thereby requesting the channel associated with that username.

According to an official Google staff post from 2013-07-11, it's not a requisite that every channel have attached an username. Hence, is perfectly possible for Channels.list endpoint to return no channel at all, if the argument of forUsername does not represent a YouTube username.

If you use one of my public (MIT licensed) Python 3 script -- youtube-search.py --, you'll see that it returns nothing for your queried username Animal Planet:

The short answer to your question is: indeed, there is an API that will provide all video metadata of your channel, including the metadata of unlisted videos.

For the longer answer, just bear with me for a while:

First thing, do note that a given video has a privacy status of the following kinds:

status.privacyStatus (string)
The video's privacy status. Valid values for this property are:

• private
• public
• unlisted

For to obtain the IDs of all videos uploaded by your channel, irrespective of their privacy status, you'll have to invoke the PlaylistItems.list API endpoint queried with the parameter playlistId set to the ID of your channel's uploads playlist, while issuing an OAuth authorized request (that is: passing to the API a valid access token; using only an API key will make the endpoint return only public videos):