The current signature of UpdateDeviceSwitchPortAsync on the ISwitchPorts section forces a SwitchPort object to be used as the request body. This enforces the caller of the endpoint to pass in the full SwitctPort object, however, making it very uncomfortable to update a single field of the port.
The Meraki API documentation (https://developer.cisco.com/meraki/api-v1/update-device-switch-port/) implies none of the fields are required on the request body.
Tested the endpoint via Postman and successfully updated the Name of the port by simply sending:
The API client should also support changing the value of a single field.
The current signature of UpdateDeviceSwitchPortAsync on the ISwitchPorts section forces a SwitchPort object to be used as the request body. This enforces the caller of the endpoint to pass in the full SwitctPort object, however, making it very uncomfortable to update a single field of the port.
The Meraki API documentation (https://developer.cisco.com/meraki/api-v1/update-device-switch-port/) implies none of the fields are required on the request body.
Tested the endpoint via Postman and successfully updated the Name of the port by simply sending:
The API client should also support changing the value of a single field.