Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why am I able to authenticate against REST API version2 and not against version3

Adam Gyõri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 21, 2026

Good evening team, we have been using JIRA REST API version 2 for quite some time, specifically the request to fetch the USER:

https://globalwebindex.atlassian.net/rest/api/2/user/search?query="

We are trying to switch to version 3 using:
"
https://globalwebindex.atlassian.net/rest/api/3/groupuserpicker?query="

For version 3 we are getting following response:
403 Forbidden
You are not authenticated. Authentication required to perform this operation.

We are using generated tokens via https://id.atlassian.com/manage-profile/security/api-tokens , then encoding the "email:token" string with BASE64. And creating request like:
curl -D- \
-X GET \
-H "Authorization: Basic encodedMailAndToken" \
-H "Content-Type: application/json" \
"https://globalwebindex.atlassian.net/rest/api/3/groupuserpicker?query=agyori@gwi.com&maxResults=50"

with response: You are not authenticated. Authentication required to perform this operation.

The thing I can not comprehend is why are we able to authenticate against version 2 and not against version 3. 

If you have any suggestion it would massively help us, thank you in advance.

2 answers

1 vote
Mikael Sandberg
Community Champion
January 21, 2026

You may want to to check the headers you are sending, based on the documentation the groupuserpicker is expecting Accept: application/json, not Content-Type.

Adam Gyõri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 21, 2026

Great point, thank you Mikael ! But still "403 You are not authenticated. Authentication required to perform this operation."
Does anything else occur to you ?

Mikael Sandberg
Community Champion
January 21, 2026

No nothing else looks odd, I just know that some endpoints are particular when it comes to the headers, for example there are Confluence endpoints that expect Content-Type instead of content-type even though headers should not be case sensitive.

Like Adam Gyõri likes this
Adam Gyõri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 21, 2026

Ok thank you though.

0 votes
Adam Gyõri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2026

Update the permission Issue seems to only be related to any request related to users.
I am without any issue able to fetch projects or a single project using: /rest/api/3/project

Could it be the case that I should probably ask somewhere for some additional permissions? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events