Why do I receive status code 410 Gone from tempo api?

Question

I am using the following endpoint in a process of syncing worklogs between 2 platforms: api.tempo.io/core/3/worklogs/jira/{worklogId}.

Everything worked perfectly for a long time until a few days ago when this endpoint started receiving 410 Gone. The code in charge of this process was not changed in a long time. I am using a build from more than half a year ago. The api token is still valid.

Salih Tuç · Answer

Thanks for the reply and the follow-up information. If you face with any challenges during that time, please don't hesitate to ask your questions in the Community!

Cheers.

Oddvin Røsand · Answer

Thanks for your reply!

I've been in contact with the Tempo team, and they could confirm that they disable v3 of their api for all new installations. That is the reason why we get different experience for different sites using the same code.

We have started a task of upgrading our implementation of their api from v3 to v4. While waiting for this task to complete I got Tempo to whitelist the sites where v3 was disabled for a limited period of time. This way our code works ok until we get our code to support v4.

Best regards,

Oddvin

Salih Tuç · Answer

Hi @Oddvin Røsand ,

As I stated in the first message, Tempo is announcing the changes and sunsets from their documentation. An endpoint may not changed at all and you can still use the earlier version, this is your decision.

However, as a best practice, I suggest to use only one version of the specific API that you are using. So, if you changed one endpoint to v4, I think you should change other ones to v4, too. Version changes are usually brings efficiency and easy access to some specific features.

In summary, you can still use the v3 since it is responding, nothing urgent right now. But, I strongly suggest that you should update it to v4 asap :)

Have a nice day!