rest api search projects | 403 | uncomprehensible error message

[Christos Paisios]

We perform a GET request on the following URL:

https://api.atlassian.com/ex/jira/{{cloud-id}}/rest/api/3/project/search

{{cloud-id}} it's a GUID for the cloud instance we want to search.

The response we get back has status code 403, Forbidden. However we get a weird error message, that we don't get:

HTTP error: 403: Tenant is restricted: migration

Could you please explain when this happens ?

Thanks in advance !

[Trudy Claspill]

Hello @Christos Paisios 

Welcome to the community.

I have not seen the "migration" reason attached to this message before, so I don't know exactly what that means. I have seen the "tenant is restricted" message with other reason that indicate access has been restricted due to non-payment or due to inactivity.

Are you able to access the site directly through the UI with a valid account?

You could have an admin for the site reach out directly to Atlassian Support for an explanation.

https://support.atlassian.com/contact/#/

[Christos Paisios]

Hello @Trudy Claspill . Thanks for the warm welcome !

So, we don't have access to the UI. On the behalf of one of our customers, who uses JIRA, we had to communicate with that instance via the API endpoint mentioned before. In that context this error occurred. It has happened so far only once. However, we would like to understand why that happened and how we should act on similar cases. To be honest, I think that neither non-payment nor inactivity would be the case for -at least that specific customer-. We communicated via your API with their JIRA instance many times a day. They do use JIRA. Hence I can't understand how this to be related to non-payment or inactivity.

[Trudy Claspill]

I was not suggesting that this happened due to non-payment or inactivity. Those examples had different text where yours shows "migration".

I am still looking for more information for that specific version of the message.

[Trudy Claspill]

Still doing research, but other Community Leaders hypothesized that there could have been a migration in the background of the host (in the cloud hosting service provider) or of the data residency location, which caused a temporary lock out on access.

I would guess that what you should do in this case is retry the API call.

I am continuing to look for documentation on this, and if I find anything I'll let you know.