Zephyr Cloud API - automated creation of execution

Hey,

thank you for your reply.

Sorry for the delay, I was away for the holidays.

Well I tried following your solution and to delete and reapply a new key and to send as a raw json.

I did not work however and I got the exact same result.

What did work was adding the cycleId in the request data itself.

From the documentation the cycleId is optional in the cloud API, however in the server API the cycleId is mandatory so this is where I got the inspiration to try it here as well.

did not work:

request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id}

did work:

request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id, "cycleId": "-1"}

This has indeed solved the problem and you can now close the post.

I do strongly suggest updating the documentation to reflect that the cycleId is indeed mandatory and not optional (or maybe change the request validation so the response is not an ambigious internal server error...)

Sincerely,