I wanted to know and understand the pricing structure of YouTube Data API v3 after the daily quota of 10,000 units is exceeded.
I understood the quota calculation.
Before requesting for additional quota by filling this form, I want to understand the pricing structure of it.
Thanks in advance
Related
I'm planning to request increasing the Google Drive API's quotas limit of "Queries per 100 seconds per user" from 10,000 to 10,000,000 drastically, because our application uses a lot of Google Drive accessing.
I'm wondering whether;
1. increasing the quota takes any costs or not
2. using this api takes any costs or not
I found the link below that users disccusses about it.
Where can I find the price list for Google Drive API?
However, it is not cleared that we can increase and use free charge or not.
Could you please give me the information about it?
As per Drive API v3 documentation.
You can request an increase in quota; you do need a billing account.
You have to make the request first, and then they will answer granting it or not, there is no public price list.
For a direct link to the quotas section in your console, follow this link
also, it is worth reading through these common errors and how to get around them.
I wants to increase the quota limit for YouTube Data API, currently they are providing only 10K units , but i wants at least of 10M units for my project. So how google charge for units, and any estimated figure to know how much they may charge to increase the quota?
I'm building a pretty large app for a client that is going to aggregate feeds from various sources. My client estimates around 900 follow-able users will be in this system to start out, with more being added over time. He wants to update the feed data every 15 minutes, so we would need to update one user feed per second, assuming 900 feeds and a 15 minute TTL. As the requests take a few seconds to complete, we would then need to load balance across a few threads to tackle the queue asynchronously.
Should I be worried about quota errors or hitting any kind of limitations? If so, what are our options?
I've already read their help pages and documentation, but it's very vague; I need concrete numbers. It's not feasible to load test their API to figure out the limitation.
Version 3 of the YouTube Data API has concrete quota numbers listed in the Google API Console where you register for your API Key. You can use 10,000 units per day. Projects that had enabled the YouTube Data API before April 20, 2016, have a default quota of 50,000,000 per day.
You can read about what a unit is here:
https://developers.google.com/youtube/v3/getting-started#quota
A simple read operation that only retrieves the ID of each returned resource has a cost of approximately 1 unit.
A write operation has a cost of approximately 50 units.
A video upload has a cost of approximately 1600 units.
If you hit the limits, Google will stop returning results until your quota is reset. You can apply for more than 1,000,000 requests per day, but you will have to pay for those extra requests.
There is a calculator provided by YouTube to check your usage. It is a good tool to estimate your usage.
https://developers.google.com/youtube/v3/determine_quota_cost
If you need to make more requests than allotted, you can request a higher quota here: https://support.google.com/youtube/contact/yt_api_form
I'm building a pretty large app for a client that is going to aggregate feeds from various sources. My client estimates around 900 follow-able users will be in this system to start out, with more being added over time. He wants to update the feed data every 15 minutes, so we would need to update one user feed per second, assuming 900 feeds and a 15 minute TTL. As the requests take a few seconds to complete, we would then need to load balance across a few threads to tackle the queue asynchronously.
Should I be worried about quota errors or hitting any kind of limitations? If so, what are our options?
I've already read their help pages and documentation, but it's very vague; I need concrete numbers. It's not feasible to load test their API to figure out the limitation.
Version 3 of the YouTube Data API has concrete quota numbers listed in the Google API Console where you register for your API Key. You can use 10,000 units per day. Projects that had enabled the YouTube Data API before April 20, 2016, have a default quota of 50,000,000 per day.
You can read about what a unit is here:
https://developers.google.com/youtube/v3/getting-started#quota
A simple read operation that only retrieves the ID of each returned resource has a cost of approximately 1 unit.
A write operation has a cost of approximately 50 units.
A video upload has a cost of approximately 1600 units.
If you hit the limits, Google will stop returning results until your quota is reset. You can apply for more than 1,000,000 requests per day, but you will have to pay for those extra requests.
There is a calculator provided by YouTube to check your usage. It is a good tool to estimate your usage.
https://developers.google.com/youtube/v3/determine_quota_cost
If you need to make more requests than allotted, you can request a higher quota here: https://support.google.com/youtube/contact/yt_api_form
how can I set the max cruising speed, if I calc a new route?
I use the Google Maps API at my site for trucks and want to set a "max speed limit" by 80 km/h. Any idea?
The Google Maps API does not provide speedlimit information or filtering, so you can't.
It should. Any travel guidance system which provides a time needs to take all sorts of factors into the calculation - just see how effective TomTom IQ routes is! It uses not only speed limits but actual real-time speed data gathered from Tomtom users. Also, I tow a caravan and so a 70mph speed on a UK motorway is not applicable, but I can set a maximum speed of 60mph (the max in the UK on motorways, if towing), which makes the transit times pretty close to reality most of the time. Google maps times are meaningless.
KC