Forum Discussion
Cisco Meraki API Host Guidance
Summary
Tenable is announcing changes to our documentation for the Cisco Meraki API integration. Customers using a “unique” host in the “Cisco Meraki Host” field of the credential should use “api.meraki.com”, or a region-specific instead if applicable. Please refer to the documentation for full guidance.
Impact
Customers using the Cisco Meraki API integration are encouraged to check their configurations and update them accordingly.
This change in guidance addresses cases where some customers were experiencing HTTP 308 redirects, resulting in integration failures. This is also closely related to cases where customers were experiencing HTTP 403 errors, which has been addressed by changes in the Cisco Meraki API Web Application Firewall (WAF).
Release Date
Dec 15th, 2025
1 Reply
We are using fedramp Meraki, and as such have always been pointed to api.gov-meraki.com until this started failing. To fix this, I started specifying the redirect location returned from Meraki (via curl), in my case it is "n2.dashboard.gov-meraki.com".
Is this expected to be required? Or should I open a ticket with support?
