Forums

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

Getting 401 on calling /rest/api/2/issue/createmeta

Daniel Radezky January 22, 2024

I'm getting weird experience using /rest/api/2/issue/createmeta. It always returns 401 error without any additional clarification but only when we use it from non-local environment and only when the we use a token that was retrieved from OAuth 1.0 authentication. OAuth 2.0 works fine.

I found some recent info that this endpoint was deprecated but it doesn't explain the error we're getting is OAuth 1.0 non-local env specific. I would appreciate any help/ideas because I am getting stuck with this one.

2 answers

1 accepted

0 votes
Answer accepted
Daniel Radezky February 1, 2024

Eventually we just replaced that endpoint with a newer one Get create field metadata for a project and issue type id and it worked

0 votes
Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 22, 2024

Hello @Daniel Radezky 

Given that the documentation for both the v2 and v3 Issue Createmeta endpoints for Jira Cloud tells you that they only support OAuth 2.0, I would have thought that in itself would be a big enough clue as to the answer.

Also, given that the use of OAuth 1.0 authentication for the entire Jira Cloud platform's REST API has been deprecated, I would have thought that too would have been another big clue.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events