This is one I have asked for a few times over the years. There is a general assumption that the API that the Meraki Dashboard UI uses is one and the same as the one exposed to develop around, it's not, they are two separate APIs, public and private, it certainly would help my Dev Team if they were one and the same, i.e. what you can do via the Dashboard UI can be done via the API, its just not the case, the public API is separately exposed and is very much use case driven, which is great, until you hit blockers, such as the one you are up against.