Topic: Authentication required when using new api (resolved)

[BarryGordon]

I used to use the free api, but since that is no longer available I have bought a PWS, set it up and started converting my program that requests and displays the weather information on my wall mounted iPads.

The URL I send (with station id and api key obfuscated) is:
 https://api.weather.com/v3/pws/obsrvations/current?stationId=KFLMxxxxxxx&format=json&units=e&apikey=xxxxxxx45a94yyyyyyyyyye45a9d5da1c

My system returns a message that states "Authentication needed". I could not find any description as to how authentication is to be provided and what it consists of. The sample requests in the api documentation do not have any authentication in them.  Do I need to supply any other https headers that are not shown in the sample request stings?

[PaulMy]

But there is still a free WU api for those that are sending data to WU.  I am using it.
Possibly the paid version gives you more...


Enjoy,
Paul

[WSWeather]

Possibly the paid version gives you more...

At $200/mo (minimum) it better cook dinner and wash your car. 

[saratogaWX]

I used to use the free api, but since that is no longer available I have bought a PWS, set it up and started converting my program that requests and displays the weather information on my wall mounted iPads.

The URL I send (with station id and api key obfuscated) is:
 https://api.weather.com/v3/pws/obsrvations/current?stationId=KFLMxxxxxxx&format=json&units=e&apikey=xxxxxxx45a94yyyyyyyyyye45a9d5da1c

My system returns a message that states "Authentication needed". I could not find any description as to how authentication is to be provided and what it consists of. The sample requests in the api documentation do not have any authentication in them.  Do I need to supply any other https headers that are not shown in the sample request stings?

If you have a NEW WU API key, then a request like

https://api.weather.com/v2/pws/observations/current?stationId=KMAHANOV10&format=json&units=e&apiKey=yourApiKey

will work.  I think you're trying to use the /v3/ instead of the /v2/ version of the query to the API.  We (PWS users) have to use what they've documented here for the API calls allowed with the new keys.

[BarryGordon]

Thanks, the correct version solved the problem.