I meant for the following to be shared with everybody accidentally hit "Reply to author" instead of "Reply". Transcript below!
------------------------------------------------------------------------------------------------------ The intent of the http referer requirement, as described in the documentation, is to accurately identify your site/app. Inclusion of a referer that points to more information (e.g. a download page) is sufficient. Also, you're correct that the userip parameter is designed for server- side, not client-side, requests. In the future, please ask your questions in the group so that everyone can benefit from the answers :) Cheers, Adam On Tue, Mar 23, 2010 at 1:37 PM, Hugo <[email protected]> wrote: Adam, what is Google's position regarding API calls from native apps? Specifically I am working on an iPhone/Android app that would make API calls. Of course the call isn't originating from a web page so there is no way that a technically accurate http referer header can be provided (however a useful referer header could be added to the request and pointing to a page describing API usage context & contact for more info...). Is there a possible exception to the "accurate http referer" rule in that context? or at least a looser interpretation? As a side note, in that case the IP seen by google would be the IP of the client, I assume that would make the use of the userip parameter irrelevant? Thanks! On Mar 5, 5:48 pm, Adam Feldman <[email protected]> wrote: > Hello, > > Are you using the userip parameter in your server-side requests? If > so, please let me know the IP address of your server and/or the http > referer that you're including with your requests (feel free to respond > here or off thread if you prefer). > > If you're making the requests client side, please post a URL to your > website. > > Either way, I'm glad to investigate and help you resolve the problem. > > Cheers, > Adam > > On Mar 5, 1:16 am, MrCoder <[email protected]> wrote: > > > Hi Adam, > > > We have added a nice "Google Translate" button to our client which > > will issue translation of all sentences in a document through ajax > > calls from java (could be thousands of calls). I have recently run > > into getting the translations banned due to possible abuse of the > > service, which makes this feature a no-no for us. Is this really > > violating anything? If so, do you have any plans of releasing some > > costly company version where it's possible to translate more than > > "Hello world" once each minute? > > > Thanks! > > /R -- 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.
