REST API calls failing with error 4xx response code after Cloud site is renamed

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Problem

As an administrator, you may have some scripts or webhooks configured that utilise Cloud REST API calls to perform operations/actions on your Jira site (E.g: Create issues, update issues).

Recently, your Cloud site went through a URL name change – after the site renamed, all the REST API calls started failing with errors with a 4xx response code (E.g: 401, 403, 404)

Cause

This is due to the tool/scripts used to perform the REST API calls still trying to reach the old site URL – currently, Jira Cloud does not have the ability to auto-redirect REST API calls from the old site name to the updated site name. 

There is a bug report raised for this limitation which can be tracked on:

Workaround

After a Cloud site has gone through a renaming, make sure to update the REST API calls used in your environment with the new site name. 



Last modified on May 30, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.