Issue with running iOS REST API commands for iOS upgrades

[habit81]

Hi, I'm facing two issues with REST API commands related to iOS upgrade schedule. Perhaps someone already managed to overcome it.

1. When running API command
   https://AW_TENANT/api/mdm/devices/SOME_UUID/osupdate I get error message ' errorCode 33, Feature is currently turned off'
   I'm running this API command to receive the name of productKey (iOS upgrade internal name) that will be used in separate API command in Issue#2


2. I'm trying to run API to actually schedule iOS upgrade with download option only. The URL should be something like this:
   https://AW_TENANT/api/mdm/devices/commands/scheduleosupdate?searchby=serialnumber&id=SOME_SERIAL_NUM...
   There is however a 4th argument called OSUpdateProductKeys that needs to be passed to API command as a json BODY. I tried constructing the body in many ways but always end up with different error message. Has someone managed to run this command successfully? If yes, please let me know how the body should look like.

Interestingly I was able to run the iOS upgrade bulk command successfully. The bulk command does not require OSUpdateProductKeys. It only requires device IDs. The documentation on https://AW_TENANT/api/help is so poorly written. It's lacking examples etc. Anyway I hope someone can give me a hint. Thanks in advance.

[JamesCorrJamesC]

I have just ran into the exact same issues, and found your post.
I opened up a support ticket requesting an example,  If they get this to me, I will post the correct format.

[JamesCorrJamesC]

Hi Jakub,
My team mostly has this figured out.  We opened a ticket and after a lot of back and forth we have found out that in order to use the new ' OSUpdateProductKeys'  parameter, you have to have a special beta feature flag enabled in your console environment.

Sine the new ' OSUpdateProductKeys'  parameter is now required, the net affect is that Airwatch has essentially bricked the whole os update API for no reason.
It's a v1 api and been around for years. Why they decided to break it instead of adding a new V2 is hard to understand.

We just had the ' OSUpdateProductKeys'  feature flag enabled, and it does look like it works again.

[CoreyWood]

James,

Where do you go to enable the ' OSUpdateProductKeys'  parameter in the console?

[JamesCorrJamesC]

We are running Dedicated SAAS, so it was a support ticket to SAAS-Opps, to have it enabled.