Forum Discussion

Borgert's avatar
Borgert
New Contributor
3 years ago

Cannot create new execution using Zephyr Squad Server REST API

I am currently trying to create a new execution for a test using this example from the API:
https://getzephyr.docs.apiary.io/#reference/executionresource/get-defect-list/create-new-execution

 

However it does not seem to work when I pass a similar request body to the given endpoint. I am able to change data on current executions by using a Put request, but apparently not perform a POST request on the endpoint provided by the API. 

What might be the cause of this? Should the admin allow such changes first, or?

 

Prerequisites:

I am -

  • Using Zephyr Squad Server.
  • Using Basic Authentication.
  • Using Content-Type: application/json - header

 

Request body (example):

{
    "cycleId": "1",
    "issueId": "26660",  
    "projectId": "32067"
}
 
Response body:
Since it's just the standard Jira 404 Not Found page, it seems redundant to include.
However, if nessecary then it can be found here: https://pastebin.com/EX1j292F
 
 
Please comment if more information is needed, thanks!
APIs
Server
Test Execution
  • Borgert's avatar
    Borgert
    3 years ago

    I figured it out.

     

    For those curious, then the problem was that I applied the example url: 

    http://localhost:2990/jira/rest/zapi/latest/execution
     

    - and replaced localhost:2990 with the hostname of our organization. However, the /jira/ would apparently also have to be deleted.

     

     

    So the API call was instead made to:

    https://jira.hostname.com/rest/zapi/latest/execution.

     

    - which worked perfectly.

     

    Maybe I was just stupid, smh.

  • Borgert's avatar
    Borgert
    New Contributor
    3 years ago

    I figured it out.

     

    For those curious, then the problem was that I applied the example url: 

    http://localhost:2990/jira/rest/zapi/latest/execution
     

    - and replaced localhost:2990 with the hostname of our organization. However, the /jira/ would apparently also have to be deleted.

     

     

    So the API call was instead made to:

    https://jira.hostname.com/rest/zapi/latest/execution.

     

    - which worked perfectly.

     

    Maybe I was just stupid, smh.