Connect Treasure Data to clariBI
Connect Treasure Data with your API key, sync your query job history, and see how your platform is being queried next to the rest of your business data.
clariBI| Connection | API connector. You paste your Treasure Data API key. |
| Access | Read-only. clariBI never writes to Treasure Data. |
| Sync | When the data is more than a day old, clariBI syncs it again before a question, dashboard refresh or report uses it. You can also press Sync now. |
| More endpoints | 19 documented Treasure Data endpoints you can add, up to 30 per source (trial, Starter and above) |
| Plans | Every plan, including Free. Asking questions in plain English needs the trial or Starter and above. |
About Treasure Data
Treasure Data is an enterprise customer data platform that stores unified customer data and runs queries against it as jobs.
clariBI reads Treasure Data through its REST API using your own API key: your query job history, with each job carrying its type, status, target database, timing, and row count. This is operational metadata about how your platform is queried, not the customer data inside it. Access is read-only, and clariBI never submits or edits a job.
Vendor site: treasuredata.com
What clariBI syncs
clariBI pulls your recent query jobs through the Treasure Data REST API, lands them as a preprocessed dataset, and refreshes them once they are more than a day old. Access is read-only.
clariBI syncs each job with its created date, type, status, target database, and row count, then builds an insights dashboard you can query, extend, or pull into reports. This is job history, the operational record of how your platform is queried, not the customer data stored inside it.
clariBI only ever reads. It never submits a query or edits a job in Treasure Data.
What you can chart
- Query jobs created over time
- Jobs by status (success, error, running, killed)
- Jobs by type (hive, presto, trino) and target database
- Rows returned and result sizes per job
- Query load lined up with releases or reporting cycles
How to connect Treasure Data
Open Data Sources in clariBI
In clariBI, go to Data Sources > Add Data Source, find Treasure Data, and paste your API key (Treasure Data console, then your profile). The key is stored encrypted.
Choose what to sync
Pick the job history resource to pull. clariBI reads it read-only.
Sync, then get dashboards
clariBI syncs the recent jobs, preprocesses them, and builds an insights dashboard. Ask "How many query jobs ran this week and how many failed?" and clariBI reads the synced job history.
Questions you can ask
Asking in plain English uses AI credits, so it needs the trial or a Starter, Professional or Enterprise plan. Totals and trends are computed from the synced rows; the AI plans the question, picks the chart and writes the explanation.
- "Did query load spike during month-end reporting?"
- "Is our job failure rate creeping up?"
About the Treasure Data connector
What do I need to connect Treasure Data?
Your Treasure Data API key (the console, then your profile). You paste it into clariBI once; the key is stored encrypted.
Does this connector read my actual customer data?
No. It reads your query job history, the operational record of how your platform is queried. Reading the customer data inside Treasure Data needs submitting a query job, which this connector does not do.
Which clariBI plans include Treasure Data?
Every plan can connect Treasure Data, within its data source limit: 3 on Free, 5 on Lite, 10 on Starter, 50 on Professional and 100 on Enterprise. Each source gets an automatic dashboard on every plan. Asking questions in plain English, AI reports and adding endpoints from the Treasure Data catalog need the trial or a Starter, Professional or Enterprise plan.
Try Treasure Data in clariBI
The trial lasts 14 days, includes 50 AI credits and needs no card. When it ends, your account moves to the Free plan and keeps its data and dashboards.