> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/9.3-administer/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp.md).

# Visualization API

The Visualization API 3.0 provides a unified way to visualize data across the Pentaho suite, including [Analyzer](https://www.hitachivantara.com/en-us/products/big-data-integration-analytics/pentaho-business-analytics.html), [PDI](https://www.hitachivantara.com/en-us/products/big-data-integration-analytics/pentaho-data-integration.html), and [CDF](https://community.hitachivantara.com/docs/DOC-1009859-cdf-dashboard-framework). This API allows for safe and isolated operation between third party applications, visualizations, and business logic.

The Visualization API 3.0 is built on top of the following Pentaho Platform JavaScript APIs:

* **Data API**

  provides seamless integration with data sources in the Pentaho platform, as well as with other client-side component frameworks.
* **Type API**

  Provides out-of-the-box features such as class inheritance, metadata support, validation, and serialization.
* **Core APIs**

  Provide underlying core features such as localization, theming and services registration, and consumption.

A set of stock visualizations is included to cover the most common chart types. Based on the [CCC](https://community.hitachivantara.com/docs/DOC-1009860-ccc-chart-components) charting library, these stock visualizations are customizable and extensible to fit your organization’s desired look and feel.

If you want to know more about the specifics of how Analyzer integrates with the Visualization API, see [Analyzer and the Visualization API](broken://pages/wkkEQ4s4YvgrynYTD7hR).

The following sections will guide you through a sample visualization for the Pentaho platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-admin/9.3-administer/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.