# Tabular Data Endpoints

## Introduction

The HDX Tabular Data Endpoints provide programmatic access to a number of tabular datasets hosted on HDX. It supports features like customizable queries and dataset joins to enable seamless integration into external tools and systems. By allowing real-time querying of tabular data, HDX Tabular Data endpoints makes it easier for developers, analysts, and humanitarian responders to automatically integrate HDX data into their workflows.

The HDX Tabular Data endpoints are powered by the [CKAN DataStore](https://ckan.org/features/datastore) extension.

The following documentation is intended for analysts and technical audiences to configure the endpoints, troubleshoot, integrate with tools, and learn from working examples.

## Building a HDX Tabular **Data** query

With your HDX API token and the `resource_id` (see [HDX Core Concepts section](https://docs.humdata.org/build/overview/hdx-core-concepts) for more information), you have the key components needed to configure an HDX Tabular Data query. The diagram below shows how these elements fit together; the different endpoints are explained in the following sections.

<figure><img src="/files/Ar0GSW8B5vtnPvSM5lWT" alt=""><figcaption><p>This diagram shows the basic elements of a Tabular Data Endpoint query.</p></figcaption></figure>

## Feedback and support

We are always adding new features and additional datasets into the Tabular Data Endpoints. If you would like to request either a new feature or think a critical dataset is missing, please let us know!

Report bugs and request features by emailing [hdx@un.org](mailto:undefined).


---

# 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.humdata.org/build/hdx-apis/tabular-data-endpoints.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.