Transition to Webcams API v3

[amonphi]

Hi,
after receiving an email saying:
"...As part of our ongoing commitment to improving our services, Webcams API v2 will be discontinued after December 31st this year. If you are currently using v2, it's imperative to transition to Webcams API v3 before the mentioned date to ensure uninterrupted service ...."

From here https://api.windy.com/keys I generated a new API Key for Wbcam, I gave the authorization as indicated in point 2 here https://api.windy.com/webcams/api/v3/docs#/Webcams API V3/PublicApiController_getWebcams but, by filling in one of the various options at the bottom of the page, for example by sending the request https://api.windy.com/webcams/api/v3/webcams?lang=it&limit=10&offset=0&categoryOperation=and&sortKey=popularity&sortDirection=asc&nearby=42.45%2C12.15%2C5&include= I get the response "Missing Header 'x-windy-api-key' with API key".

Again at point 2 here https://api.windy.com/webcams/api/v3/docs# it is indicated "For your own API requests, include the following header: "x-windy-api-key": "API_KEY"" but, honestly, I didn't understand how and where in the URL to insert the "x-windy-api-key" header: "API_KEY"".

I apologize but I'm not an expert on this.

Thank you

[kekert]

Hello @amonphi, there is a lock icon in the upper right corner of each query, you can fill the key in there.

[amonphi]

@kekert said in Transition to Webcams API v3:

Hello @amonphi, there is a lock icon in the upper right corner of each query, you can fill the key in there.

Hi, in the meantime, thanks for the support .... yes yesterday I had followed that passage and to test the bee in that example of use everything seems to work.!

However, not all the examples can make them respond correctly (maybe fill in some string incorrectly) and also I believed that I could also use the call through web browser with Request URL but, I continue to obtain the error message "Missing Header 'X- Windy-APi-Key 'with Api Key "as in the photo.

[caldrjir]

Hi @amonphi,
since the API key has to be included in the request header, instead of the query parameter, the preferred way to test our API in the browser should be by using our documentation environment.

But there are some other ways, which I would recommend for testing, like Posman which allows you to modify your headers and also generates code snippets in specified languages if needed.