After GETting a Meraki SSID slot, a developer enables it by PUTting the entire GET payload back unchanged except flipping enabled. Dashboard rejects the call. What is the sounder enable construction?
Select an answer to reveal the explanation.
Short Explanation
Replaying the whole GET is like mailing back every blank on a form—including ones marked do not write. Send a sparse enable body: enabled true and only what you mean to change.
Full Explanation
Replaying the entire GET payload on PUT sends nulls and read-only fields that Dashboard rejects (including auth/encryption extras the slot does not use). The constructed enable sends enabled: true plus any field you actually intend to change. Location API calls and empty bodies do not enable the SSID slot.