> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/guides/beam-guides/sample-demand-data.md).
# Sample demand data
If you don't have your own demand data ready, you can use one of our sample datasets to explore Beam and the Forecasts API. Each dataset contains synthetic daily demand data modeled on realistic industry patterns. Use any dataset with your own location: the industry type matters more than the specific location when getting started.
## Available datasets
PredictHQ is optimized for the following named industries: `accommodation`, `cpg`, `tourism`, `marketing`, `parking`, `restaurants`, `retail`, and `transportation`. If your business doesn't fit one of these, use `other` - the platform applies to any industry, and Beam calibrates to your own demand data either way. See [Industry recommendations](/getting-started/guides/industry-specific-event-filters.md) for guidance on choosing.
## Using the sample data
### **With Beam**
Upload the sample data to an existing Beam Analysis using the [Upload demand data](/api/beam/analyses/upload-demand-data.md) endpoint:
```python
import requests
analysis_id = "YOUR_ANALYSIS_ID"
PHQ_API_TOKEN = "YOUR_API_TOKEN"
with open("sample_demand_retail.csv", "rb") as f:
response = requests.post(
url=f"https://api.predicthq.com/v1/beam/analyses/{analysis_id}/sink",
headers={
"Authorization": f"Bearer {PHQ_API_TOKEN}",
"Content-Type": "text/csv",
},
data=f,
)
print("Upload successful" if response.status_code == 202 else response.json())
```
See the [Beam guides](/getting-started/guides/beam-guides.md) for a full walkthrough.
### **With Forecasts API**
Upload the sample data to an existing forecast model using the [Upload demand data](/api/forecasts/demand-data/upload-demand-data.md) endpoint:
```python
import requests
import pandas as pd
import json
model_id = "YOUR_MODEL_ID"
PHQ_API_TOKEN = "YOUR_API_TOKEN"
df = pd.read_csv("sample_demand_retail.csv")
response = requests.post(
url=f"https://api.predicthq.com/v1/forecasts/models/{model_id}/demand",
headers={
"Authorization": f"Bearer {PHQ_API_TOKEN}",
"Content-Type": "application/json",
},
json={"demand": json.loads(df.to_json(orient="records"))},
)
print("Upload successful" if response.status_code == 201 else response.json())
```
See the [Getting started with Forecasts API](/getting-started/guides/forecasts-api-guides/getting-started.md) guide for a full walkthrough including how to create a model and generate a forecast.
{% hint style="info" %}
We provide these datasets for testing and exploration only. For production use, replace them with your own demand data.
{% endhint %}
---
# 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.predicthq.com/getting-started/guides/beam-guides/sample-demand-data.md?ask=&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.