cancel
Showing results for 
Search instead for 
Did you mean: 

Is MV Snapshot API working now ?[20190820]

SOLVED
Here to help

Is MV Snapshot API working now ?[20190820]

Hi , All

 

Is MV Snapshot API working now?

I'm sure this API worked last week.

 

but now the following error occurs.

 
!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" 

head
  title Page unavailable -- Cisco Meraki /title

.......

 

 

If you know this reason , could you tell me it , please.

 

Regards

1 ACCEPTED SOLUTION

Accepted Solutions
Kind of a big deal

Re: Is MV Snapshot API working now ?[20190820]

Works for me. Are you using Postman?

 

Did anything change with regards to the access rights of the account whose API key you're using?

3 REPLIES 3
Kind of a big deal

Re: Is MV Snapshot API working now ?[20190820]

Works for me. Are you using Postman?

 

Did anything change with regards to the access rights of the account whose API key you're using?

Here to help

Re: Is MV Snapshot API working now ?[20190820]

Yes , I use Postman , curl , and my application (made by C#)

 

I didn't change my access right, but your comment helped me to notice about the API key 

I regenerated the API key , and tried to use the snapshot API again.

it works now.

 

Thank you , @BrechtSchamp 

I solved the issue. 

 

I didn't change the access right , but I did MV camera firmware upgrade and one MV camera moved another network in the same organization.

is this the cause of the API key changed?

 

Regards

Kind of a big deal

Re: Is MV Snapshot API working now ?[20190820]

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

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.