I am planning to develop an iOS weather application that is non-commercial which retrieves JSON feed from Yahoo's Weather API.
Documentation: https://developer.yahoo.com/weather/
However, I don't understand the purpose of needing an API-Key? I am successful in retrieving weather data by calling this URL with parameters and it gives back a JSON data. (Note: The URL below is from the JS example but same concept as if it were Objective-C)
https://query.yahooapis.com/v1/public/yql?q=select wind from weather.forecast where woeid in (select woeid from geo.places(1) where text='chicago, il')&format=json&callback=callbackFunction
The documentation says non-commercial use is restricted to 2000 queries per day, but how is this tracked if no unique keys were ever used? What is the correct "legal" way in using this API?
I found this old question being asked, however the answer wasn't sufficient: Does Yahoo Weather API needs an Consumer API Key?
Any input would be appreciated!
Side Note
- Any other FREE weather api tool that do not limit queries and are for non-commercial publication use recommend will also be accepted as an answer
Upon further research, Yahoo offers both a public and OAuth APIs for developers. The public API that is related by querying the URL given above limits users to 2,000 queries per hour per IP Address.
https://developer.yahoo.com/yql/guide/usage_info_limits.html
Related
We are building an application that manages video campaigns on DV 360. It includes uploading and changing a lot of YouTube videos on a daily basis.
We found that the YT Data API allows us to upload about 5 videos daily before we exhaust the API quota. We requested an extension via the public form. But there is no public information about the SLA for that form or how to get additional Dev support with the API. Which we will need, as our use case is different from the typical API user (apparently).
Has anybody gone through this process successfully and/or found a way to get Dev Support from Google for the YouTube Data API?
Thanks!
Your questions are indeed very much pertinent.
I can state -- based on my experience monitoring the tags youtube-data-api and youtube-api for more than three years -- that there's no official info related to SLAs and Dev Support here on SO.
The YouTube Data API is officially a free of charge API. But that does not exclude the possibility of Google offering this API under different conditions to clients willing to pay for the services provided to them.
I'd recommend to address your issues directly to Google, either through its own issue tracker site, or through its own support forum.
I am going to implement a python client that search videos on youtube with different queries. Apparently I should use youtube data api for this. Even though I read quata cost I just want to be sure that using youtube api is totally free of charge. Sorry it is too basic.
Yes, using the YouTube API does not incur any monetary cost for the entity calling the API. If you go over your quota an 403 Error will be returned by the API.
Links:
YouTube API Quota DetailsYouTube Quota Calculator
Google already provides a Python client for all of its APIs, including YouTube, which handles authentication, forming and making the API request as well as some datatype translation (i.e. JSON to dictionary, etc.). (link)
Yes it is, but some restrictions like limit you can use only 100000 units per day.
and 3000 per second per 100 user per day. For more quotas you have to apply for it. You can apply key or oauth id at HERE. Hope it will help you.
We're currently integrating Google Drive/Docs access in our mobile Apps and use the Google Document List API for this purpose. Are there any restrictions on the number of requests allowed for single API key?
I can't find any information in the Google API Console as the Document List API is not listed there. I can only activate the Google Drive API (which does not yet support functionalities we need).
The Documents List API does not use API keys in the same way as the newer APIs such as Drive. We (Google) do not give exact quota details for this API, but in general the value is extremely high. You may encounter 503 responses which indicate that you should perform exponential backoff. If, despite this, you are hitting an absolute ceiling, you should contact us and we will investigate, and look to increase your quota.
I want to parse google and yandex search results for my little website analyzer utility.
so i should send hundreds requests per minute. What is good practice for this issue?
Is google search api a good way?
The Google Search API may not be used for bots. Google will block your utility if you request too much searches.
http://code.google.com/apis/ajaxsearch/terms.html
You agree that when using the Service, You will not, and will not permit users or other third parties to:
Use any robot, spider, site search/retrieval application, or other device to retrieve or index any portion of Google Search Results or to collect information about users for any unauthorized purpose;
Does Google offer a RESTful API where I can pass it a city name (or zip) and it returns the longitude & latitude.
I know how to do this with using the Google Maps API, but I really don't want to have my users download the huge 200k Google Maps API solely so that I can geocode a location.
Does anyone know of a URL based (REST) city/zip to longitude & latitude API?
Since geocoding this information then kicks off multiple other processes, doing this first step is of critical importance to have it perform quickly b/c its a bottleneck right now using the Google Maps API b/c of the huge download and JavaScript loadup.
Yahoo PlaceFinder is a new service offered by Yahoo! that provides services for converting addresses (including city names) into latitude / longitude pairs. The service is also capable of doing the opposite (converting coordinates into an address).
Unlike Google's Geocoding API the TOS for Yahoo PlaceFinder do not forbid using the data outside of their maps API.
You could use geonames.org web sevices (or download the server)
http://www.geonames.org/export/reverse-geocoding.html
Also keep in mind that you will likely run over your quotas for the day if you have heavy traffic using the direct HTTP call method. Google limits usage based on IP address, so using the client side code will greatly increase the number of geocode lookups you can do per day since they'll be associated with user's computers rather than your server(s).
$.get("http://ipinfo.io", function(response) {
console.log(response.city, response.country);
}, "jsonp");
Here's a more detailed JSFiddle example that also prints out the full response information, so you can see all of the available details: http://jsfiddle.net/zK5FN/2/