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

andonealexandru19
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 24, 2024

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.

1 answer

1 vote
Salih Tuç
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 24, 2024

Hi @andonealexandru19, welcome to the Community!

Tempo recently sunset the v3.0, so you need to update your requests from 3 to 4.

Besides the performance changes, it is mostly the same API. The key difference is, v4 is not returning (and/or using) any text-like attributes that you can access through ids: such as issueKey, user's display name etc.

You can change your url directly to v4 and test the code. If code is working fine and you are sure that you are not using issueKey, then probably there is no problem.

For more details, you can check Tempo documentation  about changes between v3 and v4.

Oddvin Røsand October 28, 2024

Hello @Salih Tuç 

For a new site we experience 410 for 

https://api.tempo.io/core/3/account-links/project/<PROJECT_KEY>

This works for existing sites. And this endpoint is not mentioned in the link you provided. Is this also end-of-life? Where can I find documention on this? And how come it works for some sites, but not for new ones?

For the new site I got what I needed using

https://api.tempo.io/4/account-links/project/<PROJECT_ID>

But how urgent is it to fix our code so the integration towards Tempo don't stop working for existing sites?

Best regards,

Oddvin

Like Kenneth Juul Wannebo likes this
Salih Tuç
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 29, 2024

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!

Like Oddvin Røsand likes this
Oddvin Røsand October 29, 2024

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

Like Salih Tuç likes this
Salih Tuç
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 30, 2024

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.

Suggest an answer

Log in or Sign up to answer