Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Forbidden (403) error using Jira API

A 3rd party is getting a ‘Forbidden (403) error when they try to connect to our Jira instance using the Jira API. They receive the following GET request:

curl --request GET \
  --url 'https://subcom-gtsc.atlassian.net/rest/api/3/field' \
  --user 'sales@signius.com:our_token' \
  --header 'Accept: application/json'

This user is set up as a customer and therefore is not using up a license. They did not create an account, but they set up a token. The user requested a new token to see whether the token was the reason they kept getting "Forbidden (403)" error messages when trying to connect to our Jira instance.  Using the new token to connect to the API returned the same error, so they revoked the new token.  Then they thought I may need to clear all tokens in case there was some obscure issue.  So, they revoked all token's MAP had and created a new one.  Using this new token results in the same error.  Therefore, they are claiming this is NOT a token issue.

The user had tried this a month ago and it was working. They even tested this out on their own Jira instance and it worked.

 

What could have caused this on my Jira instance? Do I need to whitelist their IP Address in the Jira API?  

1 answer

1 accepted

0 votes
Answer accepted

@Fahad AkhtarIf I understand your problem correctly, the issue is caused by the requesting party not being a Jira user.  They are a customer, and have no API access.

That means you need to set them up as a full user account.

The user was saying that everything was working fine a month ago. A month ago they still had a customer account. Could it be anything else?

@marc -Collabello--Phase Locked- , your suggestion worked. Thank you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

170 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you