Thanks for your reply.   Maybe , "xConfig Network [1..1] IEEE8021X TlsVerify ..." is a wired network configuration , not wifi.   Simply I should use a radius server , not Meraki Cloud Authentication.   Thank you very much , Bruce😊 ... View more

Thanks!! ... View more

I explained that badly.   The value often changes even if the same object. ... View more

Good to hear that it's solved. The API key is linked to a user account and the snapshot endpoint will only work for accounts who have access to that camera. If the camera is moved to a network that the account has no access to, this could be the reason for it to stop working. However just regenerating a new API key shouldn't make a difference then. Maybe there was a different issue.   Since the snapshot API uses POST another possible explanation could be the well-known redirect issue. Postman handles these correctly, but not all libraries do. So in case you run into the issue again, try replacing the url by the direct shard url: Note that the request is redirected to n##.meraki.com. A 302 may happen on any API call, including those that modify state such as DELETE, POST, and PUT. When a GET is redirected, the status code will be 302. When a non-GET is redirected, the status code will be 307 for Postman, or 308 for any other client. Client applications must follow these redirects. No action will be taken by the host issuing the redirect, so even non-idempotent requests are safe to retry on the new host. Source: https://documentation.meraki.com/zGeneral_Administration/Other_Topics/The_Cisco_Meraki_Dashboard_API ... View more

You're welcome! Note that the shard might be different in other organizations so to create a more robust script you should make it follow the redirect or figure out the shard number by performing a GET on your org first.   "Note also that most HTTP libraries and clients will not follow a redirect with an HTTP verb other than GET, and may instead follow the redirect but substitute GET for the HTTP verb. As a result, you may find a redirect on DELETE, POST, or PUT will look as though a GET was requested. To avoid this, first perform a GET on the organization you are working with, and store the URL you are working with, then use that URL for subsequent requests (particularly those that modify state)." Source: https://documentation.meraki.com/zGeneral_Administration/Other_Topics/The_Cisco_Meraki_Dashboard_API ... View more