# Data Sources

When building a widget, you always need a **data source**. The data source includes all the necessary connection and authentication parameters.

{% hint style="info" %}
For the full technical reference for data sources, visit the [Data Sources](/carto-for-developers/reference/data-sources.md) reference.
{% endhint %}

Data sources are available through the CARTO submodule in deck.gl, and you can re-use your existing sources from CARTO + deck.gl layers, or build your own sources exclusively for widget use.

## Data sources compatibility

Currently, widgets are compatible with the following sources, using server-side calculations when available, and client-side calculations as a fallback.

| Data Source              | Compatible with widgets | Widget mode     |
| ------------------------ | ----------------------- | --------------- |
| **vectorTableSource**    | ✅                       | **Server-side** |
| **vectorQuerySource**    | ✅                       | **Server-side** |
| **vectorTilesetSource**  | ✅                       | *Client-side*   |
| **h3TableSource**        | ✅                       | **Server-side** |
| **h3QuerySource**        | ✅                       | **Server-side** |
| **h3TilesetSource**      | ✅                       | *Client-side*   |
| **quadbinTableSource**   | ✅                       | **Server-side** |
| **quadbinQuerySource**   | ✅                       | **Server-side** |
| **quadbinTilesetSource** | ✅                       | *Client-side*   |
| **rasterSource**         | ✅                       | *Client-side*   |
| **boundaryTableSource**  | ❌                       | -               |
| **boundaryQuerySource**  | ❌                       | -               |

{% hint style="info" %}
For **boundaryTableSource** and **boundaryQuerySource**, a recommended workaround is to use a vectorTableSource or a vectorQuerySource using the same properties, attached to the widgets. The same filters can then be attached to both sources.
{% endhint %}

## Re-using data sources for Widgets and Layers

If you plan to use the same data sources in your deck.gl layers and in your data widgets, then your existing CARTO + deck.gl data sources are totally compatible with widgets

<pre class="language-typescript"><code class="lang-typescript">import {vectorTableSource} from 'carto-api-client';
import {VectorTileLayer} from '@deck.gl/carto';

// init your data source

<strong>const data = await vectorTableSource({
</strong>    ...cartoCredentials,
    tableName: 'carto-demo-data.demo_tables.osm_pois_usa',
    filters: filters
})

// use it in a layer

new VectorTileLayer({
    id: 'places',
    pickable: true,
    data: data,
    pointRadiusMinPixels: 4,
    getFillColor: [200, 0, 80]
})

// use the same source in a widget data model

const histogram = await data.widgetSource.getCategories({
    column: 'group_name',
    operation: 'count',
    operationColumn: '*'
    spatialFilter: currentViewStatePolygon
});
</code></pre>

## Using server-side widgets without layers

When using [server-side widgets](/carto-for-developers/reference/carto-widgets-reference/server-side-vs.-client-side.md), having a layer is not a requirement. You can specify your source and build your widget without any additional layers. This is a powerful pattern to expose additional insights, use global datasets for filtering while rendering aggregated datasets, or simply to achieve advanced use cases.

<pre class="language-typescript"><code class="lang-typescript">import {vectorTableSource} from 'carto-api-client';

// init your data source

<strong>const data = await vectorTableSource({
</strong>    ...cartoCredentials,
    tableName: 'carto-demo-data.demo_tables.osm_pois_usa',
    filters: filters
})

// use the source in a widget, with no layers

const histogram = await data.widgetSource.getCategories({
    column: 'group_name',
    operation: 'count',
    operationColumn: '*'
    spatialFilter: currentViewStatePolygon
});
</code></pre>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/data-sources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.