YouTube API

26 views
Skip to first unread message

Louis Bronne

unread,
Jan 5, 2016, 11:36:06 AM1/5/16
to phrasea-support-en
Hello,

The configuration for the YouTube API requires a Developer key.
This Developer key is not provided anymore by Google, which claims it is now unuseful.

Despite of this unusefulness I've always got the message, whatever fake Developer key I give:
Erreur lors de votre authentification
Expected response code 200, got 403 <HTML> <HEAD> <TITLE>Invalid developer key</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <H1>Invalid developer key</H1> <H2>Error 403</H2> </BODY> </HTML>

Is this a simple way to impede Phraseanet from using developer key parameter within its connection to YouTube API?

Thank you.

- Louis

Louis Bronne

unread,
Jan 6, 2016, 2:14:51 PM1/6/16
to phrasea-support-en
Hi again,

I think I got it... but partially.
I needed a "OAuth 2.0 client IDs" AND a "API Key" from Google Developers.
The keys from the first one go to Phraseanet "Youtube public key" and "Youtube secret key", while the "API Key" goes to "Developper key"...

At least with that I get rid of Error 403 (Invalid developer key).

But I now have the following error message:

Expected response code 200, got 410 <errors xmlns='http://schemas.google.com/g/2005'><error><domain>GData</domain><code>NoLongerAvailableException</code><internalReason>No longer available</internalReason></error></errors>

I suppose that is because Zend 1.12.3 (*) still runs with YouTube API v2.

Did anyone already encountered such a problem ?
Does anybody know if Zend 1.12 (or directly Phraseanet) can be configured for using YouTube API v3 ? and how ?

Thank you.

- Louis


(*) The most recent release I managed to install without impeding the Bridge from running (on Phraseanet 3.8.8)

Louis Bronne

unread,
Jan 11, 2016, 5:26:29 AM1/11/16
to phrasea-support-en
In fact, it seems the Zend package on which relies the YouTube Bridge connexion is not upgraded anymore. It will then never work with YouTube API v3.

Phraseanet documentation should remove the word "YouTube" from its documentation to prevent others than me from spending hours and hours trying to understand in vain.

Yours sincerely,

- Louis



On Tuesday, 5 January 2016 17:36:06 UTC+1, Louis Bronne wrote:
Reply all
Reply to author
Forward
0 new messages