Response code 403 (Forbidden)

[nfriend]

I recently began receiving 403 errors when using google-translate-api. Digging in to the source a bit, this is the error that is being thrown:

{
    "message": "Response code 403 (Forbidden)",
    "host": "translate.google.com",
    "hostname": "translate.google.com",
    "method": "GET",
    "path": "/translate_a/single?client=t&sl=en&tl=fr&hl=fr&dt=at&dt=bd&dt=ex&dt=ld&dt=md&dt=qca&dt=rw&dt=rm&dt=ss&dt=t&ie=UTF-8&oe=UTF-8&otf=1&ssel=0&tsel=0&kc=7&q=A-Z%20Site%20Index&tk=801225.801225",
    "statusCode": 403,
    "statusMessage": "Forbidden"
}

Based on this comment, it seems that Google may have added in some rate limiting that may affect this module. Can you verify if this is the root cause?

[snowcxt]

I changed the line 35 to client: 'gtx', instead of client: 't', and it's working for me now.

[nfriend]

@snowcxt - you're right, that change worked for me as well. Do you know why this fixes the issue?

[vitalets]

I was also getting 403 but for another reason.
It was caused by getting incorrect token in dependency module google-translate-token, see #12 (there is already working pr).

The url above also has incorrect token: ...&tk=801225.801225 (notice equal numbers around dot).

Now the most interesting part.
By the comments it looks like changing client from gtx to t allows it to work with incorrect token.
I've tried the url with client=gtx and got captcha. When I passed captcha, the translation was dowloaded.

So for client=gtx token is not checked. I've tried url without token and it worked.

[snowcxt]

So, what's the best practice? Will somebody fix this bug?

[vitalets]

So, what's the best practice? Will somebody fix this bug?

I forked google-translate-api and google-translate-token and made it work.

You can try by installing:

npm i vitalets/google-translate-api

UPDATE:
Published to npm as @vitalets/google-translate-api:

npm i @vitalets/google-translate-api

See also #79 (comment)

[Fausto95]

Worked!

[Fausto95]

Could you publish it to npm? @vitalets

[vitalets]

Could you publish it to npm? @vitalets

I can make a scoped package, but frankly speaking I'm not a fan of many similar packages in npm.

Hi @matheuss, could you kindly have a look on matheuss/google-translate-token#12 and merge it? As it blocks the functionality of both packages.
Thanks in advance!

[BirkhoffLee]

I have the same issue, using @snowcxt's solution worked for me.

[snowcxt]

So, we don't need the google-translate-token at all?

[sadra]

So, what's the best practice? Will somebody fix this bug?

I forked google-translate-api and google-translate-token and made it work.

You can try by installing:

npm i vitalets/google-translate-api

Ah God, finally worked!   🤦‍♂️

[jochemstoel]

I changed the line 35 to client: 'gtx', instead of client: 't', and it's working for me now.

This is the solution to described problem. Hooray this guy @snowcxt .