We're working on migrating from the YouTube v2 comments to YouTube v3 within our our application.
We are aware of the fact that YouTube API v2 is deprecated, is there an estimated date as to when the v2 api grace period will end? It would be very helpful for us to know so we can make sure the v3 is in place before the end of the grace period.
UPDATE
Check this SO question for details about the grace period.
Comments and API v3
The only information I can find is:
Note: The YouTube Data API (v2) has been officially deprecated as of
March 4, 2014. Please refer to our deprecation policy for more
information. Please use the YouTube Data API (v3) for new integrations
and migrate applications still using the v2 API to the v3 API as well.
Which lead to April 20, 2015 which is around the same date that the Oauth deprecations where supposed to also stop working. I heard from a Googler that everything wasn't going to be shut off at once, its kind of like a rolling shut down. If its still working I think you should try and make your changes ASAP it sounds like it could stop working at anytime.
Not a 100% answer but it was to long for a comment.
Related
since 3 days the youtube Data API v3 keeps returning the same quota exceeded errors. I made some changes to drastically reduce the number of calls to the API yesterday, hoping it would reset at midnight pacific time today, but no such luck. Could somebody please look into this. The project ID is (removed), project number is (removed).
Thank you.
#TotallyFuzzy I am having same issue yesterday and when I looked into quota the daily limit was set to 0 in my google admin console and there was no way edit,
so in the end I removed and recreate the youtube API in developer console
that fixed the problem for me, here is the screenshot of new youtube API quota
I'm a developer of a program for streamers. It receives and displays various information, such as chat, super chat, sponsors. The problem is that at the moment the program is close to the limit. And this despite the fact that I increased the delay between requests, but it did not help, because every day there are new users.
How can I increase the quota for Youtube v3?
Check this quota request page for Youtube API. You'll be required to answer several questions:
This application also requires you to submit screenshots and design
documents relating to your API Client(s) and your use of YouTube
API(s). If you do not have these ready, please apply once these are
available.
Following the migration of Hangouts on Air to Youtube Live events:
"Start a Hangout on Air" button for Youtube LiveStreaming API
It seems that the hangouts API is not being retired on April 25th
https://developers.google.com/+/hangouts/support-faq
with hangouts being more focused on the "enterprise". This is going to cause various of our enterprise's critical applications to stop working. Google Enterprise support indicates that something may come along to replace the hangouts API.
Does anyone have any leads on this replacement? We'd very much like to start working with an alternative well in advance of April 25th.
Is anyone aware of any mechanism to allow a YouTube Live event (hangout type) to communicate back to a 3rd party server to indicate it's status and participants?
Many thanks in advance
Related Post:
Is it possible to create event of type "Quick (using Google Hangouts On Air)" using YouTube Live Streaming API
As everyone using the YouTube api knows, saving or caching youtube files is prohibited by the google terms of service. So how then does this app [McTube] allow users to cache videos? I googled around and apparently google reportedly told them to remove the feature. Yet a year later the feature is still there. What gives, and how can I as a developer incorporate such a feature in my app without getting kicked off the app store?
Thanks for your time :)
I'm wondering if anyone has requested and actually received an API key for the Google Maps iOS SDK. I put in my own request over a month ago now, and still nothing despite having a shipping app that is ready to make immediate use of the new SDK (and which is picking up some negative feedback due to inaccuracies in Apple's maps).
Has anyone been issued an API key for the Google iOS SDK, and if so, how long did you have to wait for it and what were the circumstances of your application (i.e. did you have an app already deployed, how popular was it, etc.)?
I'm hoping that if we can unravel the criteria Google uses to issue these keys we can allow people with pending requests to come up with an approximate estimate of when their request might be granted.
As I mentioned in this answer, I applied for access on the 13th of December, and then received an email saying I'd been approved on the 17th of December.
I have an app on the app store which used to use Google Maps, but I had to remove the maps when iOS 6 came out. Not sure if this had anything to do with it, or if I was just lucky because I happened to hear about the SDK almost immediately after Google announced the new SDK, and I applied for access right away.
When I received the email saying that I'd been approved, I was added to a google group - which is how Google sends out notifications of updates. From the looks of it that group only has 77 members, so if that's equal to the number of people which have been given access, I guess Google are rolling out access quite slowly.
UPDATE:
As of the 21st of February, it looks like the SDK is now open to everyone.