Forums

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

403 Forbidden Error on Attachment API using OAuth 1.0

Nilimesh Hait
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!
March 24, 2025

Hello Team,

We are facing 403 Forbidden Error while accessing  Attachment API (mentioned Below) Using OAuth 1.0 from our Connected APP.

API:

 

https://your-domain.atlassian.net/rest/api/3/attachment/content/{id}

We are able to access this above API from POSTMAN. But from our connected app we are facing 403 forbidden Issue.

Can anyone help us the reason for this issue or if anyone faced same kind of issue earlier please guide us. 

Thanks,

Nilimesh

2 answers

0 votes
Marc - Devoteam
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.
March 25, 2025

Hi @Nilimesh Hait 

Welcome to the community.

As mentioned by @Jim Knepley - ReleaseTEAM oauth 1 is not supported within Atlassian, only oauth 2 is.

Postman uses oauth 2 by default, so this explains why this call succeeds.

0 votes
Jim Knepley - ReleaseTEAM
Atlassian Partner
March 24, 2025

Welcome to the community @Nilimesh Hait 

If I read the API documentation (and authentication guidance) correctly, OAuth 1.0 isn't supported and you have to use OAuth 2.0 with the appropriate scopes. That would be consistent with a 403 response, but I can't speak to why Postman works.

Nilimesh Hait
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!
March 25, 2025

Thanks @Jim Knepley - ReleaseTEAM ,

We are able to access the other APIs except Attachment API using OAuth 1.0.

Suggest an answer

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

Atlassian Community Events