- Content: projects (42 routes), workbooks (31), views, custom views, data sources (25), flows (18), collections, favourites, recycle bin
- People and access: users, groups and group sets, SCIM configurations, connected apps, identity pools and authentication configurations
- Operations: schedules and tasks, extract refresh and flow jobs, subscriptions, data alerts, webhooks, Bridge clients, pools and domain maps
- Governance: Catalog databases and tables, labels, label categories and values, data-quality warnings, triggers and certification
- Analytics surfaces: Pulse metrics, definitions and subscriptions (39 routes), Ask Data lenses, the VizQL Data Service for headless queries
- 559 routes (207 read-only) on your Tableau Cloud pod ({pod}.online.tableau.com), authenticated with a personal access token
Tableau REST API Connector
Tableau Cloud REST API — sites, projects, workbooks, views and data sources, flows, Pulse metrics and subscriptions, users, groups and group sets, schedules and tasks, webhooks, data alerts, favourites, Catalog labels and data-quality warnings, connected apps, identity pools and SCIM, Bridge, virtual connections and the VizQL Data Service — registered in Apivom Atlas as 559 routes.
What you can do
Use cases
- Provision analytics access with the account — When a customer or team is created in the CRM, add the matching Tableau users to the right groups and projects, and remove them when the relationship ends.
- Deliver the right dashboard to the right person — Create or update subscriptions and data alerts on account-level views so account managers receive the customer's dashboard on the cadence the contract promises.
- Governance signals in the data catalogue — Read data-quality warnings, labels and certification status for the sources behind a dashboard and show them next to the metric a decision relies on.
Tableau's REST API administers everything on a Tableau Cloud site: the projects, workbooks, views and data sources that hold the analytics, the flows that prepare data, the users, groups and group sets that see it, the schedules, tasks and subscriptions that keep it fresh and delivered, webhooks and data alerts that react to change, and the governance layer — Catalog databases and tables, labels, data-quality warnings and certification. Newer surfaces are included: Pulse metric definitions and subscriptions, connected apps and identity pools, SCIM provisioning, Bridge for on-premises data, virtual connections and the VizQL Data Service that answers data questions without a viz. Apivom Atlas catalogues 559 of these routes, 207 of them read-only, scoped to your site on its Tableau Cloud pod, with a personal access token as the credential contract. No Apivom product workflow uses Tableau today — Apivom's own analytics run on Apivom's platform — so the connector is available to tenants who standardise on Tableau and want CRM-driven provisioning, delivery or governance tasks run from an Apivom workflow, scoped per customer.
A Tableau personal access token (name + secret) for your Tableau Cloud site and the site's server URL. The caller signs in with the PAT and sends the session credential as X-Tableau-Auth per request; the server URL becomes the per-request base URL. Secret encrypted in your Iris tenant.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Does this work with Tableau Server (on-premises)?
The connector targets Tableau Cloud: the allowed host suffix is .online.tableau.com and the per-request base URL is your pod. Tableau Server exposes the same REST API on your own host and would need a connector registered for that host.
Can it run a query without opening a workbook?
Yes — the VizQL Data Service routes query a published data source headlessly and return rows, and Pulse routes read metric definitions and insights; both are part of the catalogue and run under the same personal access token.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.