Several updates to the Dashboard API & Postman Collection!
https://documenter.getpostman.com/view/897512/2To9xm#whats-new
Return the alert configuration for this network
Update the alert configuration for this network
Manage servers for Meraki Alerts with webhooks
List the HTTP servers for a network
Return an HTTP server
Update an HTTP server
Add an HTTP server
Delete an HTTP server
Send a test webhook
Return the status of a webhook test
Aggregated connectivity info for this network
Aggregated connectivity info for this network, grouped by node
Aggregated connectivity info for a given AP on this network
Aggregated connectivity info for this network, grouped by clients
Aggregated connectivity info for a given client on this network
Aggregated latency info for this network
Aggregated latency info for this network, grouped by node
Aggregated latency info for a given AP on this network
Aggregated latency info for this network, grouped by clients
Aggregated latency info for a given client on this network
List of all failed client connection events on this network in a given time
Enable/Disable VLANs for the given network
List the syslog servers for a network
Update the syslog servers for a network
Returns video link for the specified camera. If a timestamp supplied, it links to that time.
List LLDP and CDP information for a device
Phew. So what are you going to release tomorrow?
Hi, I noticed that Wireless Health API does not work if network is of type combined but is ok if network is of type wireless.
Any chance to use this API also on combined network?
Thanks for the updates, many useful new options. Keep bringing them.
Is API support for any of the Layer 7 rules or Forwarding Rules on the roadmap?
Yes! The port forwarding rules were just released.
See the new updates here:
https://create.meraki.io/whats-new/
The port forwarding endpoint is so good. Saved me quite a bit of time this morning.
I'm really interested in being able to manage L7 rules via API though. I know it's been on the roadmap for a while, from what a Meraki SE told me last summer. We had a large project we had to pass on because the L7 rules aren't in the API yet...
I get a 404 error when trying to pull syslog info using
List the syslog servers for a network
Is there something missing in documentation?
Should be working, just tested. Maybe share your script snippet without key?
curl -X GET \ https://api.meraki.com/api/v0/networks/L_1234567890/syslogServers \ -H 'X-Cisco-Meraki-API-Key: <APIKEY>'
[ { "host": "1.2.3.4", "port": "443", "roles": [ "URLs", "Wireless event log" ] } ]
Thanks for the reply! I'm using Powershell and I modified your call and it worked.
I'm using a Powershell Module that was created by someone on this board. I don't remember who that is, my apologies for not attributing. This module didn't have the syslog call in a cmdlet so I added it.
function Get-MerakiSyslog {
param (
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[String]
$api_key,
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
# [String]
$networkId
)
$api = @{
"endpoint" = 'https://api.meraki.com/api/v0'
}
$header = @{
"X-Cisco-Meraki-API-Key" = $api_key
"Content-Type" = 'application/json'
}
$api.url = '/networks/$networkId/syslogServers'
$uri = $api.endpoint + $api.url
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$request = Invoke-RestMethod -Method GET -Uri $uri -Headers $header
return $request
} Export-ModuleMember -Function Get-MerakiSyslog
I then call the cmdlet like so:
Get-MerakiSyslog -api_key "**********" -networkID "N_660903245316689202"
This returns a 404.
I should also mention that I commented out [String] to make sure Powershell wasn't changing the networkId in any way. So its been tried with and without the commented line.
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
# [String]
$networkId
Nevermind. I had single quotes where I needed double quotes.
Carry on. Nothing to see here..... lol