Hi Jeremy I was reading your reply to Andrea's query, and it reminded me of a similar question I wanted to make. I know that end users are only allowed to use google APIs. However, I do some of my translation work with the aid of a translation memory tool called Wordfast. This tool has an free online application in the form of a website with the following URL: www.freetm.com. Now, to use this application I have to provide my details email address and password to create an account. So, although its an open website and anyone can use it, I have my own private account which I can only access...
The application allows to enter an API translation interface number that I was given when I purchased the API (I must say I cost me nothing for the time being as I haven't been able to use it much for the reason I am about to mention) fir automatic google translation. I provided that number and it was apparently working until I got an error saying that I breached a policy..., which surprised me because I am using an application I purchased and the number I entered into my www.freetm.com account was the one I was given upon purchase of the google translation API. I don't mind if I can't use the API with this website, but what concerns me is that after that I wanted to use it with my memory tool (this is not online but a translation memory software called Wordfast) and I get the same error as before... WHat do I need to do to go back to square one and be able to use the API with my own private software?? Thanks Mechi On 7 November 2011 16:16, Jeremy Geerdes <[email protected]> wrote: > The answer to your question depends on which API you're going to use. If > you're using the deprecated Web Search API, there is no published, hard > limit on the number of queries you can run. There are, however, throttling > mechanisms in place which will be triggered if you send too many requests. > If you're using the new Custom Search API, then the limit will depend on > whether or not you have enabled billing. If not, then you will be limited > to 100 queries per day. If you have, then you can set your own limit via > the APIs Console up to 10,000 queries per day. > > That said, regardless of which API you use, the TOS are abundantly clear > that you cannot utilize applications (e.g., robots, crawlers, etc.) that > would submit automated queries. In short, all queries must result directly > from some action of the end user. > > And I should also point out that, at least in the case of the Web Search > API, the estimatedResultCount (ERC) value returned is highly unreliable. In > short, there is not necessarily any direct relationship between what the > API returns as an ERC and what google.com reports as the approximate > number of results. I have not done enough testing to know if this is the > case with the Custom Search API as well. > > And since I pointed that out, I should also point out that Google's > general TOS explicitly prohibit the use of scraping applications to parse > data (e.g., the result count) off their web interface. > > Jeremy R. Geerdes > Generally Cool Guy > Des Moines, IA > > For more information or a project quote: > [email protected] > > If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > Church! > > On Nov 7, 2011, at 9:59 AM, Andrea wrote: > > > Hi all, > > I'm working on a small research project where I need to get the > > estimate number of results for a given query. > > For example, I want to get that the query "india" has 2,360,000,000 > > results, while the query "university college dublin" has 6,360,000 > > results. > > That's the only piece of information I need from Google. > > > > What would you recommend to do in this case? > > What is the query limit for this type of queries? > > > > I'm working on Java. > > > > Thanks for any hint! > > Andrea > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Google AJAX APIs" group. > > To post to this group, send email to > > [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > To view this message on the web, visit > > http://groups.google.com/group/google-ajax-search-api?hl=en_US > > For more options, visit this group at > > http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Google AJAX APIs" group. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > To view this message on the web, visit > http://groups.google.com/group/google-ajax-search-api?hl=en_US > For more options, visit this group at > http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en > -- Mercedes Rey Goitia Freelance Translator -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] To view this message on the web, visit http://groups.google.com/group/google-ajax-search-api?hl=en_US For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en
