Tempo has decommissioned the Cloud Servlet API

Topics:

Tempo Cloud

As we announced in both November and March, Tempo has decommissioned the Servlet API for all of its Cloud products effective today, April 1, 2020. The purpose in doing so is to ensure our ability to authenticate and authorize all requests and confirm that they come directly from actual users and not from malignant parties. Making this change also allows us to align with Atlassian’s security requirements for cloud applications

In place of the Servlet API, Tempo is using its public REST API to replace the following functionalities:

 
Servlet API
REST API
GetAccounts

/billingKeyList/

/accounts/

GetHolidays

/holidayList/

/user-schedule/

/holiday-schemes/ (new)

GetWorklogs

/getWorklog/

/worklogs/


/events/deleted/types/worklog/

/events/updated/types/worklog/

UpdateWorklogs

/updateWorklog/

Storing external details on the worklog will be removed.

 

You can find complete documentation about these new endpoints in our API documentation. We also have prepared a knowledge base article to provide more technical information about these changes. 

As always, please be in touch with any questions you may have.

Subscribe to our press blog

Subscribe here to receive instant notifications when a new announcement is posted.

tempo laptop