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.

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

[Issue/Question] openweather api calls return 401 with valid key #1

Open
saadqaz1 opened this issue Jan 21, 2023 · 2 comments
Open

Comments

@saadqaz1
Copy link

saadqaz1 commented Jan 21, 2023

Hello! I am trying to setup and use this component in my app however when creating and specifying the api key from openweather the component fails to load and throws a code: 401 message: invalid API Key response. I believe it is because the endpoint is being specified to use https://api.openweathermap.org/data/2.5/onecall? which is a paid subscription plan option.

When trying to hit https://api.openweathermap.org/data/2.5/forecast? with the same api key it returns a 200 json response as expected. Is there a way to change the endpoint url for the component methods?

@Ripwords
Copy link
Owner

Hmm I will take a look into this because I am not using a paid subscription for this project 😅 so I am not sure why there would be a paywall issue. My current app is still running the component fine so I don't think it's the problem

@Ripwords
Copy link
Owner

Hello! I am trying to setup and use this component in my app however when creating and specifying the api key from openweather the component fails to load and throws a code: 401 message: invalid API Key response. I believe it is because the endpoint is being specified to use https://api.openweathermap.org/data/2.5/onecall? which is a paid subscription plan option.

When trying to hit https://api.openweathermap.org/data/2.5/forecast? with the same api key it returns a 200 json response as expected. Is there a way to change the endpoint url for the component methods?

I have checked, openweather has upgraded their OneCall API to version 3.0 and there is no longer a non-subscription based option anymore. My component heavily relies on the data received from the OneCall API, I'd have to go through their free API's to update this component. Unfortunately I am unable to give you a fixed date on when i will have the time to update it.

I will try to update this component to utilize only their free API's soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants