> For the complete documentation index, see [llms.txt](https://docs.humdata.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humdata.org/build/hdx-apis/tabular-data-endpoints/available-data-and-resource-ids.md).

# Available data and resource IDs

The Tabular Data endpoints works at the resource level, meaning you query a specific file, not the entire dataset. Tabular Data API access is currently available for a subset of resources on HDX.&#x20;

We’re working on expanding coverage to include additional structured CSV resources.

#### Browse datasets active in Tabular Data Endpoints

HDX provides a pre-filtered discovery view that shows all datasets with at least one resource currently active in the Tabular Data Endpoints. You can access this view directly [here](https://data.humdata.org/dataset?fq=res_extras_datastore_active:true).

This page automatically applies a filter for resources where `datastore_active` is true, meaning the dataset contains one or more structured CSV resources available via the Tabular Data Endpoints. From this list, you can open individual dataset pages to identify the specific resource and retrieve its resource ID for programmatic access.

#### **Tabular Data** Resource ID: HDX UI <a href="#datastore-resource-id-hdx-ui" id="datastore-resource-id-hdx-ui"></a>

Here's how to find resources active on Tabular Data through the HDX UI:

1. **Navigate to the Available Datasets via Tabular Data Endpoints Page:** Go to the discovery [page](https://data.humdata.org/dataset?fq=res_extras_datastore_active:true) that lists the available datasets for Tabular Data API access.
2. **Find your dataset:** On the actual dataset page, each data resource is listed with a name, file format, and additional indicators (e.g. API access).
3. **Access Tabular Data API endpoint:** For the individual resource available within HDX’s Tabular Data endpoints, you’ll see a link to the relevant API(s) along with the resource ID. This information is essential for querying the resource programmatically.

<div align="left" data-with-frame="true"><figure><img src="/files/768lIUS4cGhg9CqGNqfY" alt="" width="563"><figcaption><p>API button</p></figcaption></figure></div>

<div align="left" data-with-frame="true"><figure><img src="/files/CYK4XsmLX4G3ZoRsuFJj" alt="" width="563"><figcaption><p>API popup</p></figcaption></figure></div>

#### Tabular Data Resource ID: HDX Metadata API <a href="#datastore-resource-id-hdx-ckan-api" id="datastore-resource-id-hdx-ckan-api"></a>

Resource ids can also be found in the HDX metadata API response. See HDX System documentation for finding the `resource_id` through the HDX metadata API.

From the response, identify the resource that corresponds to the structured data you're interested in. Sometimes datasets include multiple resources (e.g. data files, documentation). Inspect each item in the resources array and look for one where `"datastore_active": true` (if present), which indicates Tabular Data API compatibility. Note the `id` of that resource since this is your `resource_id`.

<div align="left" data-with-frame="true"><figure><img src="/files/oIswfpVpOD0tiFzHX4at" alt="" width="563"><figcaption><p>id</p></figcaption></figure></div>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.humdata.org/build/hdx-apis/tabular-data-endpoints/available-data-and-resource-ids.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
