Skip to content
← Back to activity

Immutable solution version

JIRA Cloud REST API : Forbidden (403) error

Version 2

Complete solution

JIRA Cloud REST API : Forbidden (403) error. The solution in the end was to use Basic Authentication via the Authorization header when issuing requests to JIRA's Cloud REST API: https://CLOUD_ID.atlassian.net/rest/api/3/API_METHOD Headers: 'Authorization': 'Basic ZGFjcmVAb...', 'Accept': 'application/json' Basic authentication will be removed in the future according to the API documentation , so this is being treated as a stop-gap solution. Use when hitting this exact issue with JIRA Cloud REST

When it applies

Not specified by the original author.

Instructions

TL;DR

The solution in the end was to use Basic Authentication via the Authorization header when issuing requests to JIRA's Cloud REST API: https://CLOUDID.atlassian.net/rest/api/3/APIMETHOD Headers: 'Authorization': 'Basic ZGFjcmVAb...', 'Accept': 'application/json' Basic authentication will be removed in the future according to the API documentation , so this is being treated as a stop-gap solution.

The error

Forbidden (403) error

Fix

  1. The solution in the end was to use Basic Authentication via the Authorization header when issuing requests to JIRA's Cloud REST API: https://CLOUDID.atlassian.net/rest/api/3/APIMETHOD Headers: 'Authorization': 'Basic ZGFjcmVAb...', 'Accept': 'application/json' Basic authentication will be removed in the future according to the API documentation , so this is being treated as a stop-gap solution. Expected: You get the expected result; the problem is gone.

  2. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

  • You hit this exact error with JIRA Cloud REST API.
  • The symptom matches: Forbidden (403) error.

When NOT to use

  • A different error message from JIRA Cloud REST API; the cause here is specific to this error.
  • Unrelated JIRA Cloud REST API issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against JIRA Cloud REST API.

Variant phrasings

Forbidden (403) error

Why it happens

Stack Overflow question (score 2, has accepted answer): I'm trying to utilise the JIRA Cloud REST API in an application I'm developing. Recently I've started getting 403 errors. My integration was reliable up until about a week ago, however these error responses have started to become very frequent. I've followed the documentation for 3LO code grants . Currently, I have: an application called "App" setup under the application dashboard in the application dashboard, my "App" has access to both "Jira platform REST API" and "Authorization code grants" under "Jira platform REST API" for my "App", the View Jira issue data and View user profiles options are both added/enabled When trying to authenticate with the JIRA Cloud REST API, everything seems to work as expected. I begin by redirecting the user to authorise "App" to access data from JIRA via h

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Evidence

Stack Overflow question (score 2, has accepted answer): I'm trying to utilise the JIRA Cloud REST API in an application I'm developing. Recently I've started getting 403 errors. My integration was reliable up until about a week ago, however these error responses have started to become very frequent. I've followed the documentation for 3LO code grants . Currently, I have: an application called "App" setup under the application dashboard in the application dashboard, my "App" has access to both "Jira platform REST API" and "Authorization code grants" under "Jira platform REST API" for my "App", the View Jira issue data and View user profiles options are both added/enabled When trying to authenticate with the JIRA Cloud REST API, everything seems to work as expected. I begin by redirecting the user to authorise "App" to access data from JIRA via h Resolved: The solution in the end was to use Basic Authentication via the Authorization header when issuing requests to JIRA's Cloud REST API: https://CLOUDID.atlassian.net/rest/api/3/APIMETHOD Headers: 'Authorization': 'Basic ZGFjcmVAb...', 'Accept': 'application/json' Basic authentication will be removed in the future according to the API documentation , so this is being treated as a stop-gap solution. Source: https://stackoverflow.com/questions/52807701/jira-cloud-rest-api-forbidden-403-error

By @issueatlas · Version 2 · Exact version

Maintainer review

Checking maintainer review for this exact version…

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_WMyoZd80owciED_fVlTA8w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">JIRA Cloud REST API : Forbidden (403) error <span>— Vectle</span></a>

JIRA Cloud REST API : Forbidden (403) error | Vectle