Hi @kyle-horton

Example of images:

low-resolution image (included in all-webcams.json) It is optimized to be used as a preview and the size of this one is
398x224
preview-size.jpg

high-resolution image (included in webcams/{webcamId}) It is a full-size image and the size of this one is 1920x1080
full-size.jpg

Example of result:

{ "updatedOn": "2024-09-27T00:20:18.053Z", "webcams": [ { "webcamId": 1000550952, "title": "Beinwil am See: Hallwilersee Nord 1", "viewCount": 204378, "status": "active", "categories": [ "landscape", "lake" ], "preview": "PATH/TO/IMAGE", "hasPanorama": true, "location": { "latitude": 47.26059, "longitude": 8.20506, "regionCode": "CH.AG", "countryCode": "CH", "continentCode": "EU" } }, { "webcamId": 1010004899, "title": "Beinwil am See: Hallwilersee Nord 2", "viewCount": 147620, "status": "active", "categories": [ "landscape", "lake" ], "preview": "PATH/TO/IMAGE", "hasPanorama": true, "location": { "latitude": 47.26945, "longitude": 8.21125, "regionCode": "CH.AG", "countryCode": "CH", "continentCode": "EU" } }, ... ] }

@Polina-Nozdrina hi, there was a small technical problem here👍🏻🙂

@Mad4Max thanks for the message.

Unfortunately, users can't edit the cameras themselves, but they can suggest edits, which will then be approved by an administrator to prevent errors in our database.

However, we will be very happy if you take a look at the cameras on Madeira and send us the edits. The easiest way is to click on a specific camera, then click on the Edit button, then select the field you want to change and click on the pen on the right, as seen in the screenshots below.
As for the new cameras, we'd be grateful if you'd add them at https://www.windy.com/-add-new-webcam/webcams/add

Kind regards

@wspinzynier Hi, regarding your questions, I will try to provide relevant answers for you:

Every displaying of webcam in your app is one API request, so no caching

To fulfill direct-link, you should add something like Provided by and our logo with the link from API

If you use nearby filter from here, you will get nearest webcams

@nwagenbrenner Hi there, your use case is completely okay for us if you mentioned us as a provider of these images. Also I need to inform you that free version of our webcam API has only low resolution images.

@Alexandra-Gomes-nsenses I noticed that there is no API key filled in on your end, you can do this via the Authorize button and then you will see everything necessary after clicking on Execute in the section Responses - Curl and Request URL

Hi @Heorhii-Karabetskyi,

If you want to test endpoints through the swagger, you have to include api.windy.com in Domains restriction or leave it empty, like this:
Snímek obrazovky 2023-12-12 v 10.34.12.png About the all-webcams.json endpoint, it's for the professional API tier only
Snímek obrazovky 2023-12-12 v 10.35.52.png

Best,
Jiří.

@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.

Snímek obrazovky 2023-10-02 v 17.17.59.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.