@kekert We were not aware of the the offset limit of 10000 for professional API tier. We have just followed the migration guide for V2 to V3. The response is not correct then ("Offset is over free API tier limit 10000!"). Anyway, the all-webcams endpoint sounded very promising, but after looking at the documentation, it's missing some, for us, essential data, like city and urls with detail, edit, and provider. If you guys can add this to the response, we'd be more than happy to just use this endpoint, or add the option to use query parameters to get the data we want. Then it will be sufficient for us to make only one query against the API per day. As it stands now, and I've understood the API correctly, we need to query webcams/{webcamId} endpoint for each camera we get from all-webcams, which means around 65,000 queries, to get all the information we need. I don't think this is a better way. Do you have any suggestions? -Tommy

Hi @yrprosjektgruppe. The provider's URL should be included in the webcam response as urls.provider right now. Regards, Jiří.

Hi @senaika, it should be fixed right now.

@caldrjir Perfect I can confirm the URL is now working. However it seems like the new cluster endpoint returns a lot less points on the map than previously. Would be great if that potentially could be fine-tuned a bit more.

@kekert said in Webcams V3 token for images: You don't have to save the token, it is already in the url. All you have to do is to call the API before each page load (in order to have urls of the images with fresh tokens) OK cool. I thought the token was also designed to minimize API usage.

@caldrjir that makes sense. Personally still would have loved to have a consistent response body as that helps keep my integration code clean :)

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. [image: 1696259884567-sni-mek-obrazovky-2023-10-02-v-17.17.59-resized.png]

Hi @Lakehorn, V3 is correct, but there was a little bug in it, which should be fixed right now.

@Firemap Hi, I already contacted your via email about the info.

@Caden-Crawford Hello, could you post a link to these webcams?

@Ondřej-Šutera @senaika Thanks for the clarification.

@alpinehuts This sounds interesting. I will forward the suggestion to colleagues.

@Ruairidh-Grass I am sorry, but I am not the developer to help you accurately.

@AAverin Hello, we actually do not display any ads with the free version of Webcams API. We plan to update our Terms of Use as the information is no longer relevant.

Hey Leo, just incase you got no answer back yet https://api.windy.com/api/webcams/v2/list/country=GB/orderby=popularity/limit=20?key=INSERTYOURKEYHERE Is this in the lines of what you were after? Nilesh

@Victoriam6 Hi, for those who are still searching for answer for webcams:player, image etc. you should just add &key at the end instead of ? mark, I am writing this because I lost 8hrs for this little thing, and I hope will help someone in the future.

@Korina Sorry I should have further clarified. This is an issue with LIVE streams, they do not play in natively in your timelapse player. They open in a new tab, and sometimes its an SWF file. Not sure how you guys would fix this without re-encoding the stream or getting in touch with the owners..