Hello,
I was wondering if anyone has been able to get the Sysdev REST api working from end to end?
I’ve been successful at automating the HCK/HLK testing process and am attempting to finish the whole project by using the REST api to create a submission for signing.
Where I am stuck is on downloading the Signed Files asset. Following the documentation I can get the assetID and assetName without any problems, but the call to get the SAS URL just gives me a 404. The call I am making is just a GET on “//assets/”.
If I change the assetID to the ID for the “InitialUpload” asset, it gives me the SAS URL and I can download that file no problem. I’ve tried varying the arguments but no luck. I know I can just hit “https://sysdev.microsoft.com/member/submission/.zip” to download the file, but that link needs diferent credentials that I don’t want to code into my utility and the zip file doesn’t include the DUA hlkx package and I kinda need that. Anyone have any ideas or is the service just broken?
For posterity, I’ll add a couple of notes for the other hurdles I’ve come across.
Example steps I’ve been using: https://msdn.microsoft.com/en-us/library/windows/hardware/dn800660(v=vs.85).aspx
1) Don’t bother putting the OSSelections field in your JSON when creating the submission, the server craps out when you actually specify the ProductType or QualificationLevel and it doesn’t seem to accept “Windows 8 x64”, etc. If you leave it out, the submission defaults to “Windows 8” but the actual values are pulled from the HLKX later, so it’s all good.
2) As long as the HLKX file is under 64MB (mine are always around 50MB) you don’t have to chunk the file upload, just upload the file in one BlockBlob PUT and that works fine.
When creating the upload request, the docs specify a header value “x-ms-version”, but don’t specify which version to use. I actually parse it out of the SAS url that is given, so it should always be the right version.
3) When updating the Submission in step 5, the docs say “UpdateComplete” but the field is actually “UploadComplete”, which is actually correct in the documentation for updating a submission (here)
4) Also part of the Update Submission step, the documentation says to use the URI “/”, which works but the JSON that you submit is supposed to contain ““RequestID” : “””, which doesn’t work. After some experimentation, it turns out the server will only accept "“RequestID”: “” which you will have to extract from the submission status after you create it.
I’ve sent multiple support requests and posted this question on the MSDN forums (https://social.msdn.microsoft.com/Forums/windowshardware/en-US/85ab3ee4-4f28-4dee-b7e6-a990612a0877/submission-rest-api-almost-working-but-i-cant-seem-to-download-the-signed-files?forum=whck) but have gotten no useful replies. All I received from support was (after 3 follow up emails asking if anyone is monitoring the email address) a reply adding someone to the thread who was supposed to help but who never replied.