> 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/find/accessing-and-using-data.md).
# Accessing and using data
There are two ways to download data from HDX.
1. Download directly from the dataset page
2. Download via the API
This section contains information about how to download data directly from HDX. Go to the [Build with HDX](https://docs.humdata.org/build) section for more information about accessing data through the API.
## Download directly from the dataset page
{% stepper %}
{% step %}
#### **Open the dataset page**
Every dataset on HDX has its own page with a description of the data, metadata, and a list of resources to download.
{% endstep %}
{% step %}
#### **Find the resource you want to download**
Under "Data and Resources", you will see all the resources of the dataset. Each resource has:
* Resource name and description
* Resource size
* Resource format (CSV, XLSX, etc.)
* Last modified date
* Resource ID
{% endstep %}
{% step %}
#### **Click Download**
Click the Download button to the right of the resource to download the file to your computer's default download location.
To the right of the download button, you will see a three-dot menu. From this menu, you can export the dataset metadata for that specific file in either JSON or CSV format.
{% endstep %}
{% endstepper %}
### Tips for downloading data
* **Check the size of the resource before downloading:** Large files may take time to download on slower internet connections. The size is shown in parentheses next to the resource name.
* **Bookmark important datasets:** If you may need to re-download updated versions, bookmark the dataset page for easy access.
* **Check the file format before downloading:** Make sure you have software that supports the format you are downloading.
* **Review the metadata before downloading:** Metadata provides important information about the data and will help you understand whether the dataset fits your needs.
## Getting access to 'by request' data (HDX Connect)
Some datasets on HDX are available ‘by request’ rather than for direct download - this service is called [HDX Connect](https://docs.humdata.org/publish/publish-data/preparing-and-publishing-data).
### How to access ‘by request’ data
{% stepper %}
{% step %}
#### Find the dataset
HDX Connect data on HDX are marked by a red cross icon with a tooltip that says ‘This data is by request only’. Information about the dataset will be shown on the dataset page including the description, location, time period, and data contributor.
{% endstep %}
{% step %}
#### Click 'Request Data'
From the Dataset page, click the grey Request Data button.
{% endstep %}
{% step %}
#### Log in to your HDX account
You will be asked to log into your HDX account to request the data. If you do not have an account, click ‘Sign Up’ in the top right corner of any page.
{% endstep %}
{% step %}
#### Complete the request form
Fill in the required information:
* Your name
* Your email address
* Your organization
* Your organization type
* Where you are located
* Intended use of the data
* Comments: Please add further details here that might help the data contributor evaluate your request.
{% endstep %}
{% step %}
#### Submit your request
Review the information you provided and click Submit. Your request will be sent to the data contributor and the HDX team. You will receive an email confirming your request.
{% endstep %}
{% step %}
#### Wait for a response
The data contributor will review your request and respond via email. Response times vary depending on the organization and complexity of the request. You will be able to see the status of your request from the HDX Connect Requests page in your User Dashboard.
{% endstep %}
{% endstepper %}
### Request Responses
If your request is approved, you will receive an email with instructions on how to access the data.
This may include:
* A direct link to download the data
* Instructions for accessing the data
If your request is denied, the data contributor will typically explain why. You may be able to submit a revised request with additional information. Some requests require additional review. The data contributor may contact you with questions before making a decision.
#### Tips for successful requests
* Be specific about your use case. Clearly explain what you are working on and how the data will help. Vague requests are harder to evaluate.
* Explain data protection measures. If the data is sensitive, describe how you will handle it responsibly and limit access.
* Be patient. Data contributors, especially those working in active crises, may need time to review requests. Allow at least a few business days for a response.
If you have questions about the HDX Connect process or a specific data request, email .
## Connecting HDX data to tools you use
You can access HDX data directly using data visualization and analysis tools without having to manually download and upload files. We are developing guidance on how to connect to HDX data through common tools. For the time being we have detailed guidance on linking [HDX data to Power BI](https://docs.humdata.org/build/hdx-apis/tabular-data-endpoints/how-to-query-the-tabular-data-endpoints).
If there are other tools that you would like us to consider developing more detailed guidance for, please email
---
# 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/find/accessing-and-using-data.md?ask=&goal=
```
`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.