Translate API V1 - "Suspected Terms of Service Abuse"

[Joe Lipson]

Hi,

I've just started getting "Suspected Terms of Service Abuse. Please
see http://code.google.com/apis/errors" from The V1 REST Translate
API, it's on most but not all of my requests, so I suspect whatever is
happening is not replicated across all Google servers.

As far as I can see I'm in compliance with Google's terms, all request
are real user request, I'm using a valid key and passing referrer and
end user IP address.

Wondering if it's just me or if anyone else is seeing this?

I've filled out the form on http://code.google.com/apis/errors so will
see if I get a response there.

cheers

Joe

[Jeremy Geerdes]

I will allow Adam or one of the other Googlers to follow up with you about the actual situation, but I would offer two thoughts:

1. With the imminent discontinuation of the Translate API v1, Google is cranking down on the abuse detection thresholds. This is probably what's happening.

2. The v1 API will be shut down on December 1, 2011. You will need to update your application to utilize the v2 API AND enable billing to continue using the service after that. If I were in your shoes, I would have a hard time justifying spending too much time trying to find a solution to this particular issue.

Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA

For more information or a project quote:
jrge...@gmail.com

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!

> --
> You received this message because you are subscribed to the Google
> Groups "Google AJAX APIs" group.
> To post to this group, send email to
> google-ajax...@googlegroups.com
> To unsubscribe from this group, send email to
> google-ajax-searc...@googlegroups.com
> 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

[Joe Lipson]

Thanks Jeremy,

I've been preparing for the change over to v2 for Translate, I'm
already on it for the custom search API. Hopefully I can get the extra
few months on Translate v1 before December!

Joe

On Sep 28, 12:02 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
> I will allow Adam or one of the other Googlers to follow up with you about the actual situation, but I would offer two thoughts:
>
> 1. With the imminent discontinuation of the Translate API v1, Google is cranking down on the abuse detection thresholds. This is probably what's happening.
>
> 2. The v1 API will be shut down on December 1, 2011. You will need to update your application to utilize the v2 API AND enable billing to continue using the service after that. If I were in your shoes, I would have a hard time justifying spending too much time trying to find a solution to this particular issue.
>
> Jeremy R. Geerdes
> Generally Cool Guy
> Des Moines, IA
>
> For more information or a project quote:

> jrgeer...@gmail.com

>
> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!
>
> On Sep 27, 2011, at 8:57 PM, Joe Lipson wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > I've just started getting "Suspected Terms of Service Abuse. Please

> > seehttp://code.google.com/apis/errors" from The V1 REST Translate

> > API, it's on most but not all of my requests, so I suspect whatever is
> > happening is not replicated across all Google servers.
>
> > As far as I can see I'm in compliance with Google's terms, all request
> > are real user request, I'm using a valid key and passing referrer and
> > end user IP address.
>
> > Wondering if it's just me or if anyone else is seeing this?
>

> > I've filled out the form onhttp://code.google.com/apis/errorsso will

[Adam Feldman]

Hi Joe,

I'm sorry that you received this confusing message.  As mentioned in the deprecation announcement, we've begun limiting usage of v1 of the API.  The fact that you received a "suspected Terms of Service abuse" error message is a mistake.  We're working on updating that message to clarify.

I'm glad to hear that you're working on changing over to v2, which is the appropriate long term fix.

Thanks,

Adam

[Joe Lipson]

Hi Adam,

Thanks, that makes sense. I hurriedly implemented the v2 API last
night and it seems to be working well, it's good to be able to see the
reporting v2 offers too.

I was hoping to be able to use v1 up until December but understand the
reasoning for the change.

cheers

Joe