My application uses the YouTube Data API v3 and every day I hit a limit of 10k query cost at which point my application is unusable.
I understand the old default limit was 1m (100x!) and I can find NO way to increase it. I completed the google form titled "YouTube Data API Services – Exceptions form" which is apparently the only line of contact according to cloud support and have not received any update in over two weeks. Is there ANY other way to increase it?
I had no idea google API would be the largest hurdle in my project. thanks! :)
Related
I'm trying to collect and update data using the Business Information API.
In order to get the API Calls to work, I'm only trying to get information from my business by using "Get-requests". However when calling several methods, I keep receiving the following errors:
"Quota exceeded for quota metric 'Requests' and limit 'Requests per minute' ".
Both in the Postman-calls or the OAuth 2.0 Playground (which in my eyes: should be a sandbox, ready for testing - very frustrating…).
When I look for my quota in the API settings: I'm not even able to change the requests per minute other than '0'. This makes it really hard to test/use the API.
I can't even find out which categories there are for a business location…
For your information: I've already asked for increase of the quota using the forms. But it seems google isn't really responsive in this matter.
Can this be solved?
The API shall be used to update a group of 50 (or more) locations, this instead of bulk-editing with a csv-file.
Any help would be welcome.
Thanks in advance,
Kind Regards,
Seppe
If the quota approval form was ignored, you might still have a chance via the API support (https://support.google.com/business/contact/api_default).
They might be reluctant to grant you a quota if your maximum location count is this low though - the API is designed for larger use cases.
Is it documented anywhere that it's meant for larger users? I got approved being very clear it was only for a handful of locations.
BUT even though I got approved and have access there are 3 specific quotas (all per-minute) that are set to zero, even though I have tonnes of allowance for all the non-per-minute quotas. Seems like a bug to me.
I can make 10000 "Update Location requests per day" but zero per minute.
I have a very simple message and getting the v3 youtube data api to get the list of comments. I am just fetching the list of videos and then fetching the comments (at frequency of 5 sec) to get updated messages. using the page token as needed to minimize the load and computaion.
Today after some time while internally testing the application i started getting the quota exceeded exception. I know the youtube provided by default 10000 units and since reading the comments (and videos as well) is just 1 unit, i should expect to get similar numbers.
However, the data is wrongly calculated.
Following are request details
If you see, there are 2895 total requests LiveChatMessages-> List.
However, when i go to IAM-> Quotas, it showed 14k earlier, then 12.6k in quota usage
There seems to be some problem either with the computation or with the Documentation that defines the units for queries. Can someone help please..
PS: Just using the two apis as mentioned above in screenshot. Both are list.
If you see, there are 2895 total requests LiveChatMessages-> List. However, when i go to IAM-> Quotas, it showed 14k earlier, then 12.6k in quota usage
Yes i can see that there are 2895 requests, but how do you know what the qutoa costs are for those requests. You are using the YouTube Live Streaming api for those requests. Not the YouTube-Data-api
There is no documentation of the quota cost for the YouTube Live Streaming api calls. If Google says you used all your quota then you probably have.
I would post an issue over on the issue forum asking them to document the quota cost for the calls Issue forum
I was wondering if I could get some help understanding the Youtube Data Api, specifically Google's website says: "Each project starts with 10,000 units per day, an amount sufficient for the overwhelming majority of our API users."
Is this 10,000 per person who signs in through your project then? Because 10,000 does not in any way seem sufficient! A youtube Search alone takes 100 units if I understand the documentation, so 5 people each doing 20 searches and your project is done for the day. This seems to make building a robust Youtube browser all but impossible for a user base bigger than 2.
As you can tell I'm a bit frustrated and sure I must be missing something. Any clarifications you can offer would be appreciated.
If you check the following screen
only one of the quotas says "per user" the others are project based quotas.
You have a quota of 10000 per day for the total project.
Quota cost is calculated by the request resource.
A youtube Search alone takes 100 units per request. if I understand the documentation, so 5 people each doing 20 searches and your project is done for the day.
10000 (limit) / 100 (quota cost) = 100 search requests pre day.
It sounds to me like you have understood the quota system perfectly. If you intend to make more requests than that you will need to request additional quota.
I have a daily running task that pulls down some metrics from the YouTubeAPI based a collection of products that I want to monitor the activity for. That collection of products tends to grow over time and I'd like to set up an alert for when I get close to exceeding my daily quota limit so that I can either make a quota increase request or reduce the collection's size rather than having a gap in my metrics if I hit the limit without realizing it.
Haven't found anything in the Google API documentation for being able to query your current quota consumption or even a way to set up an e-mail alert in the console itself.
I'm not opposed to having my task track its usage internally but would prefer getting those numbers directly from the API itself and try to avoid a potential bug on my end.
Well, AFAIK you cannot query it using an API request, but you can check your daily usage in the Developer Console. Just Go to the API you want to check, then on the Overview part you can check the traffic there. Then the total response code will tell you the total count that you make a request in this API.
For more information, check this documentation that tells you that:
You can see your current usage in the quota tab for your project in the Google APIs Console.
To view or change usage limits for your project, or to request an increase to your quota, do the following:
If you don't already have a billing account for your project, then create one.
Visit the Enabled APIs page of the API library in the API Console, and select an API from the list.
To view and change quota-related settings, select Quotas. To view usage statistics, select Usage.
For V2 of the YouTube Data API what are the exact limits for the quota?
I am aware that this is a frequent question, however I am yet to find any concrete answers.
Reason for Question:
I am going to querying a large pool of videos for their comments on a regular basis and would like to know when I am coming close to my quota limit, so the system can slow down. In V3 of the YouTube API, the quota limits are clearly documented. However I'm unable to use V3 of the API as it does not support the retrieval of comments (sidenote - does anyone know why?)
In v2 of the data API, the quota was not a fixed number per day as it is in v3, but instead was a limit that prevented too many requests within a short period of time. Unfortunately, I don't believe that there exists anywhere some firm documentation as to how many requests that would be or what the short period of time would be, either; generally, Youtube has always stated that if you get a quota error while making a call to v2 of the data API you should wait "a few minutes" before trying again. Here's the only official statement.
https://developers.google.com/youtube/2.0/developers_guide_protocol_error_responses?hl=en#Quota_errors
It is possible that one of the reasons for this lack of direct documentation is that there isn't a hard and fast number, but it changes in response to the current load.
In answer to your side question, there haven't been any official statements from the YouTube team about why comment retrieval hasn't yet been implemented, but it likely will be in time (as will other pieces of data retrievable via v2 but not yet via v3).