ThoughtSpot objects

ThoughtSpot objects

ThoughtSpot is a business intelligence and data analytics platform that helps you explore, analyze and share real-time business analytics and interactive insights. Besides being an interactive data analytics platform, ThoughtSpot provides a robust and guided search functionality using which business users can search data instantly. ThoughtSpot is different from other BI tools, because ThoughtSpot Search is the core of the ThoughtSpot system.

Before you look at the rest of the developer documentation, please review this page to understand how ThoughtSpot works relative to other tools you may be familiar with.

Object model hierarchyπŸ”—

The following figure illustrates the object model hierarchy in ThoughtSpot.

Object Model Hierarchy

Data modelingπŸ”—

You must create a data model comprising at least one connection with one table to begin using Search data to create content. Most often there will be multiple tables, with a variety of joins defined in ThoughtSpot, with a Worksheet bringing those tables together into a presentable analytic data model for the end-users.

Data engineers with Can manage data privilege can add connections either in the UI or via REST API. Connections are owned and accessible only to their creator, who then imports tables from the connection. Once imported, tables can be shared with other Thoughtspot groups and users.

Tables can have Row Level Security (RLS) rules that filter the data results based on the signed-in username or the ThoughtSpot groups to which the user belongs, and those rules apply to any Worksheet that uses the table.

Data modeling workflowπŸ”—

  1. Create a connection to a cloud data warehouse.

  2. Import tables from the connection.

  3. Create worksheets (analytic data models) based on tables.

  4. Create ThoughtSpot views or SQL views as necessary.

ThoughtSport supports programmatic deployment of data models through Spotapps, scriptability, and data representation in ThoughtSpot Modeling Language (TML).

Content creationπŸ”—

ThoughtSpot Search data creates a single table or chart view based on the query in the search bar and other configurations to the view made after the search results are visible.

Search data serves the role of report builder or widget designer, while Liveboards serve the role of dashboards in other tools. A single search can be saved as an Answer object, or the search result can be pinned to a Liveboard.

A Liveboard is a collection of many visualizations presented in a defined layout. You do not create the visualizations on a Liveboard directly; they are created from search data results and then pinned to a Liveboard. You can create a new Liveboard from the Liveboards page and then add a visualization from the search data result, or you can create a new Liveboard when pinning an Answer retrieved from search data.

Content creation workflowπŸ”—

To create content:

  1. Use the Search data functionality to build visualizations from data sources such as worksheets or views.

  2. Save the search result as an Answer or pin it to a Liveboard as a visualization.

Visualizations on a LiveboardπŸ”—

You can add any number of visualizations retrieved from the search to a Liveboard object. Pinned visualizations exist only within the Liveboard and are independent of the objects saved as answers.

Each time you pin a search result, a separate new visualization is created on the Liveboard.

To edit a visualization on a Liveboard:

  1. Go to the Liveboard.

  2. Navigate to the visualization.

  3. Click the More menu the more options menu and select Edit.

Visualizations on a Liveboard have their own GUIDs, but the visualization objects do not exist separately from the Liveboard object.


Tags allow you to organize your objects and find them easily.

A tag object is created by the administrator, is visible to all users, and can be assigned by any user.

Tag search is always an OR operation: filtering on multiple tags results in all objects with any of the tags, not just those with all of the specified tags.

Access control (sharing)πŸ”—

ThoughtSpot’s access control model works by an author or administrator sharing objects to ThoughtSpot groups or other individual users:

  • The creator of an object is referred to as the author.

  • The author can share the object with their groups using the Shareable property.

  • The author can share the object with other users in Shareable groups that the author belongs to, and if the other user is also marked Shareable.

An administrator user can share any object with any group or user with no restrictions. ThoughtSpot administrators can add users locally in the UI or via REST API. Similarly, they can manage groups and sharing privileges by using the Groups feature in the UI or via REST API.

Single sign-onπŸ”—

If SAML or OpenID Connect (OIDC) integration support is enabled on your instance, users that authenticate to external identity providers (IdP) can log in to ThoughtSpot with their Single Sign-On credentials. Embedded ThoughtSpot instances also support the trusted authentication method to sign in their application users.

Object properties in REST APIπŸ”—

The object representations in ThoughtSpot REST API include the following properties:

  • id
    GUID of the object. Unique within a given ThoughtSpot instance

  • author
    GUID of the user who created / uploaded the object, or had the object transferred to them.

  • owner
    GUID representing the relationship between hierarchical objects, For example, a column would have the GUID of a table or Worksheet as owner.

  • created
    timestamp of object creation

  • modified
    timestamp from last time object was modified

  • modifiedBy
    GUID of the user who last modified the object

  • tags
    An array of tag objects representing the tags assigned to the object.

Object names in REST API v1πŸ”—

The object type names in the ThoughtSpot REST API v1 differ from the current names seen in the ThoughtSpot UI. Data objects have both a type and a sub-type within the REST API, allowing you to request all valid data objects or specify the individual sub-type.

The following notation is used in REST API v1 for the object types:



  • Data objects: LOGICAL_TABLE, with subtypes:

    • Tables: ONE_TO_ONE_LOGICAL

    • Worksheets: WORKSHEET


    • SQL views: SQL_VIEW

    • CSV imported data: USER_DEFINED

  • Connections: DATA_SOURCE

  • Tags: TAG

  • Users: USER

  • Groups: USER_GROUP



Column and join objects with their own GUIDs do exist within the ThoughtSpot system, but they are connected to tables, worksheets, or other data objects. Columns and joins can be viewed or modified only within the context of the data object to which they belong.