ThoughtSpot Python API Docs | dltHub

Build a ThoughtSpot-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

ThoughtSpot offers REST APIs for managing users, sessions, and data objects. The latest documentation is available at https://docs.thoughtspot.com/cloud/10.11.0.cl/public-api-reference.html. For getting started, refer to https://developers.thoughtspot.com/docs/rest-api-getstarted. The REST API base URL is two common base URLs used by ThoughtSpot REST APIs: - REST API v1 base: https://<THOUGHTSPOT_HOST>/tspublic/v1 - REST API v2 base: https://<THOUGHTSPOT_HOST>/api/rest/2.0 and all requests require an authenticated session (login) — session cookies or an auth token obtained via the session APIs..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading ThoughtSpot data in under 10 minutes.


What data can I load from ThoughtSpot?

Here are some of the endpoints you can load from ThoughtSpot:

ResourceEndpointMethodData selectorDescription
metadata_listvizheaderstspublic/v1/metadata/listvizheadersGET(top-level array)Lists Liveboards/visualization headers (example response is a top-level JSON array)
userstspublic/v1/user/GETGet details of users (see API reference)
user_listtspublic/v1/user/listGETGets all users, groups, and their inter-dependencies
connection_listtspublic/v1/connection/listGETLists data connections configured on the cluster
admin_configinfotspublic/v1/admin/configinfoGETGets cluster configuration details
logs_topicstspublic/v1/logs/topics/{topic}GETRetrieves audit/security logs for the given topic
session_infotspublic/v1/session/infoGETGets information about the current session

How do I authenticate with the ThoughtSpot API?

ThoughtSpot REST APIs require an authenticated user session. Typical flows: POST /tspublic/v1/session/login with username/password (returns session cookies), or use POST /tspublic/v1/session/auth/token for trusted authentication to obtain a token; include returned session cookies with subsequent requests. All requests must include header X-Requested-By: ThoughtSpot and a User-Agent header; set Accept: application/json.

1. Get your credentials

  1. Obtain a ThoughtSpot user account with Developer or Administrator privileges from your ThoughtSpot admin. 2) Use those username/password credentials for API access. 3) To create a trusted token flow, request Support or your admin to configure trusted authentication and call POST /tspublic/v1/session/auth/token as documented. 4) In browsers use the REST Playground (Develop > REST Playground v1/v2) to experiment and confirm permissions.

2. Add them to .dlt/secrets.toml

[sources.thoughtspot_source] username = "your_username" password = "your_password"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the ThoughtSpot API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python thoughtspot_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline thoughtspot_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset thoughtspot_data The duckdb destination used duckdb:/thoughtspot.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline thoughtspot_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads metadata_listvizheaders and user_list from the ThoughtSpot API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def thoughtspot_source(username, password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "two common base URLs used by ThoughtSpot REST APIs: - REST API v1 base: https://<THOUGHTSPOT_HOST>/tspublic/v1 - REST API v2 base: https://<THOUGHTSPOT_HOST>/api/rest/2.0", "auth": { "type": "http_basic", "password": username, password, }, }, "resources": [ {"name": "metadata_listvizheaders", "endpoint": {"path": "tspublic/v1/metadata/listvizheaders"}}, {"name": "user_list", "endpoint": {"path": "tspublic/v1/user/list"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="thoughtspot_pipeline", destination="duckdb", dataset_name="thoughtspot_data", ) load_info = pipeline.run(thoughtspot_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("thoughtspot_pipeline").dataset() sessions_df = data.metadata_listvizheaders.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM thoughtspot_data.metadata_listvizheaders LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("thoughtspot_pipeline").dataset() data.metadata_listvizheaders.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load ThoughtSpot data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for ThoughtSpot?

Request dlt skills, commands, AGENT.md files, and AI-native context.