As long as you are abiding by the TOS, the API key is not required. However, if you're using the RESTful side of the API (which it appears that you are), you are required to provide a valid HTTP_REFERER header. In the case of web applications, this would be the name of the page which is calling the API. In the case of non-web or desktop applications, I would strongly suggest creating a webpage of some sort, somewhere, which contains a description of the application and a means to contact you. You can then use this page as your HTTP_REFERER headers AND to generate your key if you chose to use one.
Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com [email protected] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Apr 30, 2010, at 3:39 AM, Lizard wrote: > Hi everyone, > > What key to use in the "Api language", but not from the website, but > on an application form. > > http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&q=HelloWorld&langpair=en|es&key=?????????????????? > > -- > 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]. > For more options, visit this group at > http://groups.google.com/group/google-ajax-search-api?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]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
