A parks Wi-Fi automation job calls api.meraki.com to manage SSIDs. Which authentication header is the classic Dashboard construction?
Select an answer to reveal the explanation.
Short Explanation
Meraki Dashboard expects its own key in X-Cisco-Meraki-API-Key—like a branded city ID, not a Webex or DNA Center badge taped over it.
Full Explanation
Constructed Meraki Dashboard calls authenticate with the org API key in X-Cisco-Meraki-API-Key (Bearer API-key is an alternate documented scheme; DEVCOR-era materials emphasize the classic header). A Webex Bearer or DNA Center X-Auth-Token on api.meraki.com is the wrong platform header. FDM tokens likewise do not authenticate Dashboard.