Tableau REST API

Name: Tableau REST API API
Brand: Tableau REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness IntelligenceapiKey17 EndpointsREST

For Agents

Configure Tableau analytics extension settings and manage Ask Data lenses on Tableau Server and Tableau Cloud through a JSON REST API.

Quickstart

Get started with Tableau REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list tableau analytics extension connections"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Tableau REST API API.

Read and update server-level analytics extension settings via /api/-/settings/server/extensions/analytics

Read and update site-level analytics extension settings

List, create, update, and delete analytics extension connections per site

Set or remove the analytics extension connection that a specific workbook uses

GET STARTED

Start building with Tableau REST API API

Explore with Jentic

View OpenAPI Document

Use for: I need to allow a new analytics extension connection on a Tableau site, I want to change which analytics extension a workbook uses, List all analytics extension connections registered on a Tableau site, Get the current server-level analytics extension settings

Not supported: Does not author dashboards, manage data sources, or run extracts — use for analytics extension governance and Ask Data lens management on Tableau Server and Tableau Cloud only.

Jentic publishes the only available OpenAPI document for Tableau REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Tableau REST API, keeping it validated and agent-ready. This slice of the Tableau REST API focuses on analytics extension settings and Ask Data lenses on Tableau Server and Tableau Cloud. It lets administrators configure server- and site-level analytics extension policies, register external analytics extension connections, and manage which connection a workbook uses. It also exposes Ask Data lens management, including listing and creating lenses for guided natural-language analytics. This is the right surface for ops teams automating BI governance rather than dashboard authoring.

Use Cases

Patterns agents use Tableau REST API API for, with concrete tasks.

★ Governing Analytics Extensions Across Sites

Tableau admins responsible for many sites can use the analytics extension settings endpoints to enforce consistent policy — turning extensions on, off, or restricting to a vetted list of connections. Pulling current settings via GET and pushing PUTs from a config repo turns Tableau analytics extension governance into a code-reviewed change. This is essential when extensions call out to external compute that may run customer data through a third party.

GET /api/-/settings/site/extensions/analytics for each site, then PUT the policy that matches the desired baseline.

Self-Service Workbook Extension Binding

When a workbook author requests a different analytics extension, an admin can rebind the workbook through PUT /api/-/settings/site/extensions/analytics/workbooks/{workbook_luid}/selected_connection without opening the Tableau UI. The same endpoint set lets a service desk script confirm which connection a workbook is using and remove it on offboarding. This shortens the request loop for analytics extension changes.

PUT /api/-/settings/site/extensions/analytics/workbooks/{workbook_luid}/selected_connection with the new connection LUID.

Provisioning Ask Data Lenses

Teams rolling out Ask Data to business users can create lenses programmatically through POST /api/-/askdata/lenses, scoping each lens to a curated dataset and synonym set. Listing lenses via GET supports a self-service portal that shows users which lenses are available to them. This avoids hand-clicking lens creation when a department onboards dozens of analysts.

POST /api/-/askdata/lenses with the dataset, synonyms, and permissions for each new business team.

AI Agent Auditing Tableau Extension Usage

An AI agent acting as a governance assistant can call Tableau through Jentic to enumerate analytics extension connections, list which workbooks bind to each connection, and flag any drift from policy. The Tableau auth token sits in the Jentic vault and the agent works from declared schemas, so audits are repeatable and the agent does not need read access to the Tableau admin UI. This pattern fits well alongside other governance agents over BI tooling.

Search Jentic for 'list tableau analytics extension connections', load GET /api/-/settings/site/extensions/analytics/connections, and execute, then iterate workbook bindings.

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for tableau rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/-/settings/site/extensions/analytics

Get site-level analytics extension settings

PUT

/api/-/settings/site/extensions/analytics

Update site-level analytics extension settings

GET

/api/-/settings/site/extensions/analytics/connections

List analytics extension connections

POST

/api/-/settings/site/extensions/analytics/connections

Create an analytics extension connection

PUT

/api/-/settings/site/extensions/analytics/workbooks/{workbook_luid}/selected_connection

Set the selected connection for a workbook

GET

/api/-/askdata/lenses

List Ask Data lenses

POST

/api/-/askdata/lenses

Create an Ask Data lens

GET

/api/-/settings/site/extensions/analytics

Get site-level analytics extension settings

PUT

/api/-/settings/site/extensions/analytics

Update site-level analytics extension settings

GET

/api/-/settings/site/extensions/analytics/connections

List analytics extension connections

POST

/api/-/settings/site/extensions/analytics/connections

Create an analytics extension connection

PUT

/api/-/settings/site/extensions/analytics/workbooks/{workbook_luid}/selected_connection

Set the selected connection for a workbook

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Tableau credentials and the X-Tableau-Auth session token are stored in the Jentic vault. Agents never see the raw user/password or token — Jentic injects the header at execution time.

Intent-based discovery

Agents search by intent (e.g., 'list tableau analytics extension connections') and Jentic returns the matching Tableau operation with its input schema, so the agent does not need to read the Tableau REST API reference.

Time to first call

Direct Tableau integration: 1-3 days for sign-in flow, X-Tableau-Auth handling, and LUID resolution. Through Jentic: under an hour to make the first analytics extension or Ask Data call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Tableau Platform API

Broader Tableau platform endpoints for workbook and site management

Use the help.tableau.com slice for analytics extensions and Ask Data; use the broader Tableau platform API for site, project, and workbook lifecycle.

Alternative

Google Sheets API

Spreadsheet-based reporting and lightweight BI

Choose Sheets when reporting is small enough to live in a spreadsheet; choose Tableau when governed dashboards and analytics extensions are needed.

Complementary

Airtable API

Operational database that can feed Tableau as a data source

Pair Airtable as the source of operational data with Tableau for governed dashboards and Ask Data.

FAQs

Specific to using Tableau REST API API through Jentic.

Why is there no official OpenAPI spec for Tableau REST API?

Tableau publishes documentation but no fully validated OpenAPI specification for these endpoints. Jentic generates and maintains this spec so that AI agents and developers can call the Tableau REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Tableau REST API use?

These endpoints use Tableau's session token via the X-Tableau-Auth header. Tokens are obtained from Tableau's sign-in flow on the parent server. Jentic stores the credentials used to obtain a token in its vault and supplies the X-Tableau-Auth header at execution time.

Can I list analytics extension connections on a Tableau site?

Yes. GET /api/-/settings/site/extensions/analytics/connections returns the connections configured for the site, including their LUIDs and connection metadata. Use the LUID with the /workbooks subpath to bind a specific workbook to a chosen connection.

What are the rate limits for the Tableau REST API?

Tableau Cloud applies per-site rate limits that vary by edition; Tableau Server is bounded by host capacity. Cache settings reads where possible and avoid tight loops over the analytics extensions connections list.

How do I create an Ask Data lens through Jentic?

Search Jentic for 'create a tableau ask data lens', load the POST /api/-/askdata/lenses schema, and execute with the dataset reference and lens metadata. Jentic supplies the X-Tableau-Auth header from the vault.

Can I rebind a workbook to a different analytics extension?

Yes. PUT /api/-/settings/site/extensions/analytics/workbooks/{workbook_luid}/selected_connection sets the selected connection for a specific workbook. DELETE on the same path removes the binding entirely.