403 - The request is missing a valid API key. -- inconsistently

6,985 views
Skip to first unread message

Bj Tenney

unread,
May 21, 2018, 1:11:21 PM5/21/18
to Google Cloud Translation API

I can call the google translate api using http post with the following setup in postman:


I can run this request and it will work several times, and then it fails with:
{
    "error": {
        "code": 403,
        "message": "The request is missing a valid API key.",
        "errors": [
            {
                "message": "The request is missing a valid API key.",
                "domain": "global",
                "reason": "forbidden"
            }
        ],
        "status": "PERMISSION_DENIED"
    }
}

I can then run it again, and things work again for several requests and it fails.  It's inconsistent and may fail a couple times in a row, and then start working again.



The information in this email is confidential and should only be used by the intended recipient.
If you are not the intended recipient, then you are notified that you have received this email in
error and any use, review, dissemination, distribution, copying, or acting in reliance upon this
information is strictly prohibited. Please contact the sender and delete this information from your
computer.

George (Cloud Platform Support)

unread,
May 21, 2018, 4:40:56 PM5/21/18
to Google Cloud Translation API
Have you tried switching browsers and also networks? 

To rule out possible browser-related problems, you may try submitting the same text through a curl command, as detailed on the "Quickstart" page

This forum is meant more for expressing opinions and general discussion; for such problems as 403 errors it is advisable to open an issue in the public issue tracker

Bj Tenney

unread,
May 21, 2018, 4:54:26 PM5/21/18
to Google Cloud Translation API
Thanks!  I wasn't sure what the correct place to post issues was.

George (Cloud Platform Support)

unread,
May 22, 2018, 12:42:11 PM5/22/18
to Google Cloud Translation API
Hello Bj, 

You may now follow related developments in your public tracker issue
Reply all
Reply to author
Forward
0 new messages