Forum Discussion

Talsht's avatar
Talsht
New Contributor
4 years ago

Zephyr Cloud API - automated creation of execution

Dear Community, I'm new to Zephyr cloud so pardon is the issue seems obvious to you.   I've been using the ZAPI to certain endpoints as described in the documentation so far successfully but encou...
API
execution
Zapi
  • BibekBehera's avatar
    BibekBehera
    4 years ago

    Talsht 

     

    Please update delete and regenerate the api keys and give it a try.

    Also please send the data as  raw >>JSON, it should do the trick. 

     

    If you are still facing the same issue please feel free to create a support case and we will be happy to help you!

     

    -Bibek

     

Talsht's avatar
Talsht
New Contributor

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,

gat-bryszard's avatar
gat-bryszard
New Contributor
4 years ago

We've encountered the same problem and your solution resolved it Talsht, thank you!

+1 to updating the docs, guys.