Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

XRay GET teststatuses results in a 404 error



I started testing the XRay REST API as a trial first.

I created the API Key and put it in the POST Request

Then I used the created token and put it in the GET Request Header as (Authorization Type: Bearer Token using Postman).


Response: 400 Cannot GET /rest/raven/1.0/api/settings/teststatuses


What is wrong? Did I forget a step?





3 answers

0 votes
David Boo I'm New Here Apr 13, 2022

I have the same issue when I am using Server/DC API.

Cloud API works for me, but this API is very limited. And Jira native API doesn't provide the methods that I need. For example, get the iterations of steps.

404 "null for URI": xxxxxx, this issue is an error that Jira sends when the API doesn't exist and is not managed by Jira native API. 

@Rogério Paiva - Xray Xporter , @Deepak Sharma want to use Server/DC, like me, because Xray documentation says clearly 



  • The URIs for resources have the following structure:


         For example, http://yourserver/rest/raven/2.0/api/test/TEST-123/step

@Deepak Sharma says clearly that the issue is when he uses the API */raven/*, As you can see Xray CLOUD API documentation, CLOUD API doesn't use this extension within the API URL.


Please, Has someone been able to execute XRay Server/DC API outside the Jira test ('') environment?



0 votes

Hi Ikigai,

The correct documentation for the REST API is the one found here, which is the latest documentation.
The error you are getting means the request you made was not correct, probably it was not correctly set up.

Please contact us through our support channel and send us screenshots of the request so that we can investigate and assist you.


Best regards,

Team Xray

I am also trying to connect with Xray using API mentioned in document but everytime I am getting 404.

My sample URL: "htttps://

However all the rest API, non raven one I am able to access:

Example: "htttps://

Everytime I am trying to access non-raven api, same host is giving result but all the APIs mentioned in xray documentation with raven, I am getting 404.

Could you please help me with the same. 


The test status you are referring to is the one present in this documentation:, that means you are using Server/DC version of Xray (we also have the Cloud version that differs in some aspects due to limitations in each version).


If that is the case please make sure that you are authenticating, not with token, but passing the user in the curl command as defined in the above documentation:

Example Request

curl -H "Content-Type: application/json" -X GET -u admin:admin http://yourserver/rest/raven/1.0/api/settings/teststatuses


Hope it helps.

Thanks for the response.

I tried with below combinations:

requests.get("https://{server}", auth=("{username}","{API_Token}"))                                                                         
Response: 404

requests.get("https://{server}", auth=("{username}","{Password}"))

Response: 401


requests.get("https://{server}{issue_id}/editmeta", auth=("{username}","{API_Token}"))

Response: Metadata JSON (As expected)

In both the cases raven API is not connecting with Xray, Please let me know, what I am missing.
Like Alex Garcia likes this

Hi @Deepak Sharma 


From your description, you are using Xray Cloud.

And Xray Cloud is a different app from Xray DC/Server.

You must have been looking at Xray DC/Server documentation, but the REST API is different from the Xray Cloud.

This REST API endpoint doesn't exist in Xray Cloud:



In Cloud, you need to GraphQL API instead. Please check the cloud documentation:


Thank you.

Kind regards,
Rogério Paiva [Xray Support Team]

Like Alex Garcia likes this

Nobody can help here?

Documentation Versioning is very confusing. The mentioned endpoints are different depending of the documentation version.

But trying the 2 endpoints give still 404 error...

The only requests which are working for me are the ones without the raven in path like:


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

330 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you