Creating Client VPN users - Authorization zone syntax

[ABSMSP]

Does anyone have a working JSON snippet for POSTs to the Create Network Meraki Auth User endpoint (/networks/{networkId}/merakiAuthUsers) for "Client VPN" type users?

The API reference only lists "ssidNumber": integer , presumably for creating 802.1x users. For the Client VPN, based on the response to the GET call, I am guessing it is "authorizedZone" : [MX's name], but the API doesn't seem to agree with me, as my POST returns "The following required parameters are missing: 'email' and 'authorizations' "

My body looks like this:

{
"email": "[email protected]",
"name": "Test User",
"password": "example password",
"accountType": "Client VPN",
"emailPasswordToUser": true,
"isAdmin": false,
"authorizations": [

{

"authorizedZone": "Main - appliance",

"expiresAt": "Never"

}

]

}

[ABSMSP · Accepted solution]

I have figured out my problem. In my testing, I was only specifying 'Authorization' in my header, and that has not been an issue with any other Meraki endpoint I was interacting with. When I added 'Content-type':'application/json', my function worked as desired.

But for anyone else's reference on creating "Client VPN" users, the "authorizations" parameter is in fact expecting "authorizedZone" with the format of "[your security appliance's name] - appliance"