Google GeolocationAPI Requested entity was not found

Question

So Im trying to use the Google GeolocationAPI. It sends the quest successfully and also authenticates successfully with my api key but it returns me this

    {
        "error": {
            "code": 404,
            "message": "Requested entity was not found.",
            "errors": [
                {
                    "message": "Requested entity was not found.",
                    "domain": "global",
                    "reason": "notFound"
                }
            ],
            "status": "NOT_FOUND"
        }
    }

The url Im requesting to is https://www.googleapis.com/geolocation/v1/geolocate?key=MY_KEY with post as described in the documentation.

Thanks in advance

What is the question? Did you read the docs to see what the errors are? — charlietfl, Aug 25 '20 at 19:41
There is no specification about this error actually as far as I've seen it there is no specification for any error — F4LS3, Aug 25 '20 at 20:15
If you send an adrress or lat/long you get a response. If it can process that response it sends back location data, if it can't it sends back an error message like you receieved. That is documented — charlietfl, Aug 25 '20 at 20:30
So you say Im not sending enough data for the api to give me results? — F4LS3, Aug 25 '20 at 20:33
Not sure....you haven't shown you are sending anything other than api key — charlietfl, Aug 25 '20 at 20:33
const googlePosition = await asyncFetch("https://www.googleapis.com/geolocation/v1/geolocate?key=MY_KEY", 'POST'); thats what Im doing I thought that api would locate where I am — F4LS3, Aug 25 '20 at 20:35
I am also having same issue. did you get it resolved?. can you tell me what was the issue exactly? @F4LS3 — Ashok, Sep 10 '20 at 09:48
I had a similar error, it helped just to wait and after a while it corrected itself. It is not clear why. — skywind, Oct 06 '22 at 08:37

sebacruzd · Accepted Answer · 2020-09-09T13:44:38.653

4

I recommend you to check out the documentation:

As you can read:

Before you start developing with the Geolocation API, review the authentication requirements (you need an API key) and the API usage and billing information (you need to enable billing on your project).

I was getting the exact same error until my billing information was validated. How I realized it, was using the geocoding API, which does return a better error.

edited Sep 09 '20 at 13:44

answered Aug 26 '20 at 17:45

sebacruzd

76
5

1

In the documentation its says: "The request body must be formatted as JSON. The following fields are supported, and all fields are optional" – F4LS3 Sep 06 '20 at 10:26
You are right @F4LS3 I updated the answer. I was having the exact same error and that did fix it. – sebacruzd Sep 09 '20 at 13:44
My account is a verified billing account.But still I am facing the same issue. Can you please check my [question](https://stackoverflow.com/questions/66167163/unable-to-execute-rest-api-via-curl)? – Moeez Feb 12 '21 at 06:56
@Moeez I answered your question but it was removed soon after that. I recommend you try making a request to Geocoding, because the errors in that API are more helpful than in Geolocation. I hope you can fix your problem. – sebacruzd Feb 26 '21 at 14:22

score 0 · Answer 2 · answered Oct 12 '21 at 10:11

0

You need to create and associate a billing account to your project. It will work immediately.

answered Oct 12 '21 at 10:11

mth

1

score 0 · Answer 3 · answered Dec 24 '21 at 14:13

0

We started getting a 404 error just because our credit card expired and Google could not bill us. When we updated the billing information the API came to life again.

answered Dec 24 '21 at 14:13

Au Ris

4,541
2
26
53

score 0 · Answer 4 · answered Feb 07 '22 at 12:46

0

usually, this error occurs when user access is revoked.

answered Feb 07 '22 at 12:46

Bilal Tariq

639
4
7

Google GeolocationAPI Requested entity was not found

4 Answers4