Ошибка 401 bitrix

asked Oct 12, 2015 at 23:48

The docs open by telling you that you need to register for an API key first.

To access the API you need to sign up for an API key

Since your url doesn’t contain a key, the site tells you you’re not authorized. Follow the instructions to get a key, then add it to the query parameters.

http://api.openweathermap.org/data/2.5/forecast/daily?APPID=12345&q=...

answered Oct 13, 2015 at 1:37

Error:
Invalid API key. Please see http://openweathermap.org/faq#error401 for more info

API calls responds with 401 error:
You can get the error 401 in the following cases:

• You did not specify your API key in API request.
• Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use.
• You are using wrong API key in API request. Please, check your right API key in personal account.
• You have free subscription and try to get access to our paid services (for example, 16 days/daily forecast API, any historical weather data, Weather maps 2.0, etc). Please, check your tariff in your [personal account]([price and condition]).

here are some steps to find problem.

1) Check if API key is activated

some API services provide key information in dashboard whether its activated, expired etc. openWeatherMap don’t.
to verify whether your key is working ‘MAKE API CALL FROM BROWSER’
api.openweathermap.org/data/2.5/weather?q=peshawar&appid=API_key

replace API_key with your own key, if you get data successfully then your key is activated otherwise wait for few hours to get key activated.

2) Check .env for typos & syntax

.env is file which is used to hide credentials such as API_KEY in server side code.
make sure your .env file variables are using correct syntax which is
NAME=VALUE

API_KEY=djgkv43439d90bkckcs

no semicolon, quotes etc

3) Check request URL

check request url where API call will be made , make sure

• It doesn’t have spaces, braces etc
• correct according to URL encoding
• correct according to API documentation

4) Debug using dotenv:

to know if you dotenv package is parsing API key correctly use the following code

const result = dotenv.config()

if (result.error) {
  throw result.error
} 
console.log(result.parsed)

this code checks if .env file variables are being parsed, it will print API_KEY value if its been parsed otherwise will print error which occur while parsing.

Hopefully it helps

answered Dec 13, 2020 at 12:58

I also faced the same issue, I have just created an account on open weather map and also verified the email, tried to load the api using several different url , but they replied with 401 , api key not found.

Solution: after 1 hour they all started working, so the reason was for activation it took 1 or some more hours.

For a graduate i was helping, he had a correct api key and it was active, but the api was incorrectly 401 when no content type was given

it was a simple as adding a Content-Type: application/json, and hey presto the api started working

curl command

curl --location \
  --request GET \
  'https://api.openweathermap.org/data/2.5/forecast?lat=55&lon=-3&appid=xxx' \
  --header 'Content-Type: application/json'

answered Aug 17, 2022 at 7:47

RoyRoy

1371 gold badge1 silver badge8 bronze badges

answered Sep 10 at 6:16

asked Oct 12, 2015 at 23:48

The docs open by telling you that you need to register for an API key first.

To access the API you need to sign up for an API key

Since your url doesn’t contain a key, the site tells you you’re not authorized. Follow the instructions to get a key, then add it to the query parameters.

http://api.openweathermap.org/data/2.5/forecast/daily?APPID=12345&q=...

answered Oct 13, 2015 at 1:37

Error:
Invalid API key. Please see http://openweathermap.org/faq#error401 for more info

API calls responds with 401 error:
You can get the error 401 in the following cases:

• You did not specify your API key in API request.
• Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use.
• You are using wrong API key in API request. Please, check your right API key in personal account.
• You have free subscription and try to get access to our paid services (for example, 16 days/daily forecast API, any historical weather data, Weather maps 2.0, etc). Please, check your tariff in your [personal account]([price and condition]).

here are some steps to find problem.

1) Check if API key is activated

some API services provide key information in dashboard whether its activated, expired etc. openWeatherMap don’t.
to verify whether your key is working ‘MAKE API CALL FROM BROWSER’
api.openweathermap.org/data/2.5/weather?q=peshawar&appid=API_key

replace API_key with your own key, if you get data successfully then your key is activated otherwise wait for few hours to get key activated.

2) Check .env for typos & syntax

.env is file which is used to hide credentials such as API_KEY in server side code.
make sure your .env file variables are using correct syntax which is
NAME=VALUE

API_KEY=djgkv43439d90bkckcs

no semicolon, quotes etc

3) Check request URL

check request url where API call will be made , make sure

• It doesn’t have spaces, braces etc
• correct according to URL encoding
• correct according to API documentation

4) Debug using dotenv:

to know if you dotenv package is parsing API key correctly use the following code

const result = dotenv.config()

if (result.error) {
  throw result.error
} 
console.log(result.parsed)

this code checks if .env file variables are being parsed, it will print API_KEY value if its been parsed otherwise will print error which occur while parsing.

Hopefully it helps

answered Dec 13, 2020 at 12:58

I also faced the same issue, I have just created an account on open weather map and also verified the email, tried to load the api using several different url , but they replied with 401 , api key not found.

Solution: after 1 hour they all started working, so the reason was for activation it took 1 or some more hours.

For a graduate i was helping, he had a correct api key and it was active, but the api was incorrectly 401 when no content type was given

it was a simple as adding a Content-Type: application/json, and hey presto the api started working

curl command

curl --location \
  --request GET \
  'https://api.openweathermap.org/data/2.5/forecast?lat=55&lon=-3&appid=xxx' \
  --header 'Content-Type: application/json'

answered Aug 17, 2022 at 7:47

RoyRoy

1371 gold badge1 silver badge8 bronze badges

answered Sep 10 at 6:16

Running into the same issue.

This is a duplicate of #16 (which has a typo in its title)

The problem is that the new api they use is 3.0 and it seems the project is using `/data/2.5/onecall` instead of [`data/3.0/xyz`](https://openweathermap.org/api) I don’t think there’s a way to get the a key to the old 2.5 API

@obatola unfortunately, that’s not the issue, as I show in #16. Here’s an example of calling the 2.5 endpoint, just like the workflow does, with a new key (generated a week or two ago):

♠ https "api.openweathermap.org/data/2.5/onecall?lat=42.394722&lon=-71.109103&appid=$API_KEY"
HTTP/1.1 200 OK
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: GET, POST
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 20137
Content-Type: application/json; charset=utf-8
Date: Mon, 03 Oct 2022 12:43:28 GMT
Server: openresty
X-Cache-Key: /data/2.5/onecall?lat=42.39&lon=-71.11

{
    "current": {
        "clouds": 75,
        "dew_point": 277.35,
        "dt": 1664801007,
        "feels_like": 278.17,
        "humidity": 72,
        "pressure": 1024,
        "sunrise": 1664793812,
        "sunset": 1664835790,
        "temp": 282.12,
        "uvi": 0.88,
        "visibility": 10000,
        "weather": [
            {
                "description": "broken clouds",
                "icon": "04d",
                "id": 803,
                "main": "Clouds"
            }
        ],
        "wind_deg": 60,
        "wind_gust": 12.86,
        "wind_speed": 9.26
    },
# snip

Having the same issue here . 401 Unauthorized. Is there any work around at this stage? It looks like a great workflow…

@obatola, @stallowin, I’m not sure what to tell y’all; I can use the workflow, with OpenWeather, with a freshly generated API key, without any issues.

You can see my example request via the CLI, using the same endpoint as the workflow, in my previous comment as well, demonstrating it works.

On top of that, an HTTP 401 Unauthorized means that you’re successfully reaching OpenWeather, but your credentials aren’t valid. This isn’t an issue with the workflow (if we were sending a malformed request, we’d see an HTTP 500 error).

I recommend trying out your API key directly via the command line or a browser, and seeing how that works.

It’s possible, though I’ve created new API keys to try & rule that out.

The /weather endpoint, as you point out, isn’t identical & offers far less info, so some reworking is needed if that’s the way forward.

I don’t have any time right now to dig in further, so I welcome any of y’all to give it a go & see what you turn up. I recommend reaching out to OpenWeather & seeing what they say.

I was getting the same issue with a recent account/token. 30min after I received the email «OpenWeatherMap One Call 3.0 account activation», the workflow started working. So I guess we just need to wait?

@rougeth well now, that is very interesting. Seems like maybe there is an extra step to enable the /onecall endpoint? Or they manually enable something?

@rougeth about how long did it take for you to receive that email? I’ve only be active for about 3 days so I wonder if there is some engagement or timeline?

@jeffbyrnes seems weird, right?

@zalary to be precise, a minute after receiving the e-mail «OpenWeatherMap Account created», no delay there.

@rougeth did you subscribe to the one-call API and input your credit card?

Running into the same issue here
I will check again tomorrow in case time is a factor, although my key has been generated more than 1h ago, and calling the endpoint I received from their email shows the api is already active

Having the same issue, any outcome ??

@thomasXwang I tried what you did but yet no luck on mysids … still showing same issue even I tried to generate and input new API.