YouTube Data API returns "Access Not Configured" error, although it is enabled : <p>My internally used web solution to retrieve YouTube video statistics that is based on this example (<a href="https://developers.google.com/youtube/v3/quickstart/js" rel="noreferrer">https://developers.google.com/youtube/v3/quickstart/js</a>) now fails to work. Not sure when exactly it happened, but it used to work couple of months ago.</p>

<p>I now tried to run unedited example code (apart from adjusting the CLIENT_ID, of course), and I am getting exactly the same error:</p>

<pre><code>{
    "domain": "usageLimits",
    "reason": "accessNotConfigured",
    "message": "Access Not Configured. YouTube Data API has not been used in project 123 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=123 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",
    "extendedHelp": "https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=123" }   ],   "code": 403,   "message": "Access Not Configured. YouTube Data API has not been used in project 123 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=123 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."  
}
</code></pre>

<p>When I check the YouTube API in developer console, it shows enabled status, and the Credentials compatible with this API include the ID used to authenticate the client. I can see the statistics for credential use increment when I retry the API call attempts, and the metrics reflect the number of requests and also show that the error rate is 100%. But there is no extra info on those failed attempts in the console to help on debugging the problem.</p>

<p>I have deleted and recreated API key and OAuth key, but that did not change anything.</p>

<p>Had there been any extra info on those errors on the developer console side, for example client quote exceeded, I could see how to fix this. Now I am completely stuck.</p>
