Deprecation announcements
- Deprecated features
- REST API v1 Playground deprecation
- Sage and Ask Sage deprecation
- Delete and update connection API v2 endpoints
- IAMv1
- Search assist
- Classic experience for Liveboards, Answers, and SpotIQ
- Page title customization
- Application background customization via UI
- Deprecation of customCssUrl parameter
- Deprecated parameter in REST API v2.0 authentication token endpoints
- Deprecated parameters in Version Control APIs
- Deprecation of REST API v2 (Beta) endpoints
As ThoughtSpot applications evolve, some existing features will be deprecated and replaced with new and improved functionality. A deprecated feature may continue to be functional for a short period, but will not be maintained or supported with new workflows and functionality in subsequent releases.
Deprecated features🔗
Feature | Impacted interface and release versions | Deprecation date | End of Support / removal from the product |
---|---|---|---|
ThoughtSpot Cloud 10.14.0.cl and later | November 2025 | November 2025 | |
| September 2025 | September 2025 | |
REST API v2
| November 2024 | September 2025 | |
| November 2024 | June 2025 (tentative) | |
| September 2024 | November 2024 | |
Application UI
| February 2024 | August 2024 | |
Application UI
| February 2024 | August 2024 | |
Application UI
| July 2024 | September 2024 | |
ThoughtSpot Embedded interfaces
| June 2024 | July 2024 | |
jwt_user_options parameter | REST API v2.0 authentication token endpoints
| May 2024 | June 2024 |
REST API v2 version control APIs
| March 2024 | April 2024 | |
REST API
| September 2022 | January 2023 | |
REST API v1 Playground deprecation🔗
The REST API v1 Playground experience that is currently available from the Develop page of the ThoughtSpot UI will be removed from the UI in the 10.14.0.cl release version.
- Impact on your instance
-
Only the REST API v1 Playground will be removed from the ThoughtSpot UI. However, the REST API v1 endpoints will still be available for API calls from client applications and will continue to function as usual.
- Recommended action
-
When the REST API v1 Playground is no longer available in the ThoughtSpot UI, use the REST API v1 Reference Guide for information about the REST API v1 endpoints, request and response flows. Additionally, ThoughtSpot recommends that you gradually migrate your application workflows to REST API v2 endpoints. The REST API v2 framework is regularly updated with new enhancements and bug fixes, and also offers a more standardized API experience.
Sage and Ask Sage deprecation🔗
The Sage Search (the legacy Natural Language Search interface) and Ask Sage features will be deprecated in version 10.13.0.cl, which is scheduled for release in September 2025. Along with this, the SageEmbed library in the Visual Embed SDK will also be deprecated.
- Impact on your instance
-
This change will impact all ThoughtSpot instances and applications that use the Natural Language Search (legacy) interface embedded using the SageEmbed library in Visual Embed SDK.
- Recommended action
-
Customers using the legacy Natural Language Search interface and Ask Sage in their embedding applications are advised to upgrade to Spotter. We recommend that you start using Spotter by the 10.11.0.cl release (July 2025), so that you have sufficient time to test your rollout.
Spotter provides advanced natural language search capabilities and a conversational interface to allow users to interact with the AI analyst and ask follow-up questions. To know more about Spotter and learn how to embed Spotter in your embedding application, refer to the following documentation:-
For additional queries and assistance, contact ThoughtSpot Support.
Delete and update connection API v2 endpoints🔗
The following Connection API v2 endpoints are deprecated and will be removed from the product in September 2025:
Effective from
ThoughtSpot Cloud 10.4.0.cl
Recommended action🔗
Use the following API endpoints to update and delete connection objects:
Note that the connection_identifier
in both these endpoints is a path parameter and must be included in the request URLs for update and delete operations.