Install Jentic One Beta

Connect the Tableau REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tableau REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhelp.tableau.com%2Ftableau" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhelp.tableau.com%2Ftableau" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Tableau REST 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

List Ask Data lenses available on a Tableau site

GET STARTED

Start building with Tableau REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Tableau REST 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 your Jentic One instance 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

GET

/api/-/askdata/lenses

List Ask Data lenses

POST

/api/-/askdata/lenses

Create an Ask Data lens

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Tableau REST API by hand means signing in to exchange credentials for an X-Tableau-Auth token, carrying that token on every call, and pointing requests at your own Tableau Server or Tableau Cloud host. Through Jentic you install once, import the Tableau REST API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

These analytics-extension and Ask Data settings apply at the site level and the target travels in the request body, so limit the agent to the operations it needs, such as listing analytics extension connections or reading Ask Data lenses. You choose the operations it may call, so writing extension settings or creating a connection is only included if you add it.

Credential isolation

Your Tableau credentials and the X-Tableau-Auth session token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Tableau analytics extension connections' or 'read Ask Data lenses', and Jentic returns the matching Tableau operation with its input schema so the agent calls the right endpoint without reading the Tableau REST API reference.

FAQs

Specific to using Tableau REST 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Tableau REST API?

Yes. Because you run Jentic One yourself, you decide which Tableau operations the agent may call, so you can grant it read-only actions like listing analytics extension connections (GET /api/-/settings/site/extensions/analytics/connections) or reading Ask Data lenses (GET /api/-/askdata/lenses) and withhold the rest. Write operations such as updating site-level analytics extension settings, creating a connection, or rebinding a workbook are only available to the agent if you add them. These settings apply at the site level and the target travels in the request body, so scoping the allowed operations is how you control the blast radius.

Help Tableau Tableau REST API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness IntelligenceapiKey17 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

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 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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B-Signals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

68%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tableau REST API to your agent

Capabilities

Start building with Tableau REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Help Tableau Tableau REST API

Jentic AI Readiness Score

Tableau REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness