GET that works in Postman fails from Python script

[Les Marsyla]

I have an admin role in 2 Jira projects in our environment.

I use REST API from Python to create data extracts for reporting and integration work. I have written GET for Epic issues from each project. I test the GET in Postman and it works for each project.

Postman code - https://jira-aes.kp.org/rest/api/2/search?maxResults=5000&jql=project=35600%20and%20issuetype%20=%2010100%20AND%20status%20CHANGED%20AFTER%20-1w   This GET returns a 200 code and multiple issues 

Postman code - https://jira-aes.kp.org/rest/api/2/search?maxResults=5000&jql=project=52400%20and%20issuetype%20=%2010100%20AND%20status%20CHANGED%20AFTER%20-1w This GET returns a 200 code and multiple issues

The sole difference between these two GET statements is the project

When I execute the exact same GET url via Python, the GET for project 52400 works just like in Postman.

When I execute the exact same GET url via Python, the GET for project 35600 fails with this error;

Execution time = 2026-01-30 10:10:05.586541 *****************************************
Issue get string = https://jira-aes.kp.org/rest/api/2/search?maxResults=20000&jql=project=35600%20and%20issuetype%20=%2011100
Request headers = {'Accept': 'application/json', 'Content-Type': 'application/json', 'Authorization': 'Bearer {************}'}
Request response status code = 400
Request Response text = {"errorMessages":["A value with ID '35600' does not exist for the field 'project'."],"errors":{}}

These are executed within the same 5 minute span. What could be causing this issue?

[Evgenii]

Hi. @Les Marsyla 

It's strange. According to error Jira thinks, that you're trying to get project by ID. Have you tried using project name in JQL, using doublequotes, like project="PROJECT_NAME"?

[Derek Fields _RightStar_]

I'm not sure why this would cause your error, but I notice that the issuetype is different between Postman and Python versions.

I assume that you have tried executing the JQL directly in Jira?

[Les Marsyla]

Actually, since I posted the question I had a session with our internal expert, who discovered a permissions issue in the project that was not working. The problem has been resolved.