REST API not returning any data with API token

Serge Prud'homme

Trying to fix an old script that used Basic Auth to connec to JIRA.
I see Basic Auth is no longer supported.

I read the following but although the queries return 200, they return no data.  

https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/

 

Here is the curl and output when using "-u":

curl -D- \
 -u serge.prud.homme@erxxxxxn.com:COb....64A \
 -X GET \
 -H "Content-Type: application/json" \
 https://NAME.atlassian.net/rest/api/2/search?reporter=serge.prudhomme

HTTP/2 200
server: AtlassianProxy/1.15.8.1
vary: Accept-Encoding
cache-control: no-cache, no-store, no-transform
content-type: application/json;charset=UTF-8
strict-transport-security: max-age=315360000; includeSubDomains; preload
date: Wed, 05 Feb 2020 13:22:12 GMT
atl-traceid: fbxxxxxxxxxxxxxx
x-arequestid: dfc1xxxxxxxxxxxxxxx8c3ea
x-xss-protection: 1; mode=block
timing-allow-origin: *
x-content-type-options: nosniff
set-cookie: atlassian.xsrf.token=BFK5-xxxxxxxxxxxxxxxxxxxxxxxx_lout; Path=/; Secure

{"startAt":0,"maxResults":50,"total":0,"issues":[]}


Same results if I try to create the header myself:

curl -D- \
 -X GET \
 -H "Authorization: Basic c2VyZ2UucHJ...2NSbWQ4OFF4TVAxbnJKS1AyNjRB" \
 -H "Content-Type: application/json" \
 https://NAME.atlassian.net/rest/api/2/search?reporter=serge.prudhomme

HTTP/2 200
server: AtlassianProxy/1.15.8.1
vary: Accept-Encoding
cache-control: no-cache, no-store, no-transform
content-type: application/json;charset=UTF-8
strict-transport-security: max-age=315360000; includeSubDomains; preload
date: Wed, 05 Feb 2020 13:23:37 GMT
atl-traceid: 70xxxxxxxxxxxxxx
x-arequestid: fa0a03xxxxxxxxxxxxxxxxxxx
x-xss-protection: 1; mode=block
timing-allow-origin: *
x-content-type-options: nosniff
set-cookie: atlassian.xsrf.token=BFK5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxt; Path=/; Secure

{"startAt":0,"maxResults":50,"total":0,"issues":[]}

Dario B

Hi @Serge Prud'homme ,

Thanks a lot for pasting the curl output when executing the call. 

By looking at it I can see that:

1. You are using an email address that is not present in the Jira instance you are sending the request to: the email address associated to your name in the given instance is serge.prudhomme@cxxx.xxx
2. The syntax used to call the /rest/api/2/search endpoint is not correct, it should be: https://NAME.atlassian.net/rest/api/2/search?jql=reporter=serge.prudhomme

    

You can double check this by doing the following:

• Send the exact same request with curl without providing any authentication credentials and see that the exact same response is returned:

  curl -D- -X GET https://NAME.atlassian.net/rest/api/2/search?reporter=serge.prudhomme

• Send the above request but with the right syntax (adding jql= before the actual search query) will return a more meaningful error message:

  {"errorMessages":["Field 'reporter' does not exist or this field cannot be viewed by anonymous users."],"warningMessages":[]}

• Try to log-into the Jira instance using the same email address (serge.prud.homme@exxxxxxx.xxx) and run the search from there. 

 

I hope this explains.

Also, I am going to edit your question in order to removed the sensitive data from there.

 

Cheers,
Dario