Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Google API & Charge #8

Open
rihlsul opened this issue Jan 26, 2016 · 2 comments
Open

Google API & Charge #8

rihlsul opened this issue Jan 26, 2016 · 2 comments

Comments

@rihlsul
Copy link

rihlsul commented Jan 26, 2016

Since Google API charges, the question is: Clearly this script is going to have limited success.

Can it be configured to use the Paid Google Translate API?

Ref: https://cloud.google.com/translate/v2/pricing
@kkpoon
Copy link

kkpoon commented Jan 28, 2016

Updated the API in #9 and also create another translator with Microsoft Translator

@rihlsul
Copy link
Author

rihlsul commented Mar 4, 2016

I've grabbed the code in #9, signed up for a Google API, got my key, verified it worked in Chrome via simple URL testing.

But, my Hubot is throwing: Message: The Web Token must have a signature at the end. The incoming token did not have a signature at the end of the token.

The only things I'm finding that might suggest a solution are to switch my Node.js query engine entirely.

Edit: For clarity, I did set the API_KEY environmental value correctly. I tweaked the robot.emit on errors to include what it was sending, and it spat out the right key. It's like the .get() isn't sending the query options:

<html><body><h1>Argument Exception</h1><p>Method: Translate()</p><p>Parameter: </p><p>Message: The Web Token must have a signature at the end. The incoming token did not have a signature at the end of the token.</p><code></code><p>message id=5005.V2_Rest.Translate.B94F853</p></body></html>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kkpoon @rihlsul