SOAP API End of Life Announcement

NOTE as of January 31, 2022: We know that many members are currently working through the SOAP to REST API conversion and the impact that the current world situation is having on these efforts. In order to help our members, we are committed to continuing support of the SOAP API through the Version 16 upgrade deadline. We will continue to evaluate the needs of our community and adjust the timeline as necessary. The legacy SOAP API will no longer function or be supported as of the installation of Tessitura v16.  Please also read this article, which is our most recent communication about the SOAP API end of life.

  

Tessitura-powered websites communicate with the Tessitura database via our SOAP API (Application Programming Interface). In 2009 we announced the Next Generation architecture of Tessitura, which included, over time, replacing the SOAP API with a newer and more flexible REST API. Since Version 11, we have continued to build and add to the REST API while simultaneously providing support for the legacy SOAP API.

The Version 14 release of Tessitura, completes the build out of our new REST API. This means that for the first time with v14, the REST API will include all of the functionality of the legacy SOAP API plus much more.

As we have said with each release of Tessitura since 2011, it has always been our intent to phase out support and maintenance for our legacy SOAP API. We want to give organizations as much time as possible to move to the new API and we feel that having at least a two year transition will give organizations time to plan for this change.

Transitioning to the new API will mean different things to different members. If you use TN Express Web (TNEW) to power your web transactions, then your transition will be as simple as following the standard TNEW upgrade path. The majority of Tessitura organizations now use TNEW for their web transactions, and if your organization currently has a custom Tessitura website, this may be an opportunity for you to consider that option.

If you have a custom website or custom applications that use the SOAP API to access Tessitura data then you will need to work with your web vendors or application developers to make the transition. We know that many of the web vendors in the Tessitura ecosystem have been working towards this transition for some time now by structuring their code in anticipation of the change. As these projects sometimes require a lot of planning, we highly recommend that you begin to plan this transition now.

The SOAP to REST Transition Guide lists the SOAP API methods and their corresponding functionality in the new REST API. In addition there will be sessions at the Tessitura Learning & Community Conference in July 2018 on the SOAP to REST transition, just as we have done in the previous three conferences. We will also be holding SOAP to REST transition webinars.

The REST API is the foundation for all new Tessitura development and we are proud to offer this functionality to all of our members. The REST version of the API was started as part of the Next Generation Project in which we changed the architecture of the Tessitura platform to be more modern and more easily able to connect with other applications and technologies. We are glad that with the release of Version 14 the REST API has all the capability needed to power your websites and external applications. If you have any questions please contact hello@tessituranetwork.com and we will be glad to assist you.