> ## Documentation Index
> Fetch the complete documentation index at: https://docs.felixfusion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying datasets

> How to work effectively with FelixFusion dataset query routes.

## Core workflow

Most integrations follow this sequence:

1. `GET /v1/datasets` to find a dataset id
2. `GET /v1/datasets/{dataset_id}` to inspect schema-like metadata
3. `GET /v1/datasets/{dataset_id}/query` to retrieve rows

## Common filters

Dataset queries can be shaped with parameters such as:

* `start_time`
* `end_time`
* `time`
* `publish_time`
* `columns`
* `page`
* `page_size`
* `limit`
* `order`

## Example: time-bounded query

```bash theme={null}
curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.felixfusion.ai/v1/datasets/ercot_load/query?start_time=2026-05-18T00:00:00Z&end_time=2026-05-18T06:00:00Z&order=asc"
```

## Example: selected columns

```bash theme={null}
curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.felixfusion.ai/v1/datasets/ercot_lmp_real_time_5_min/query?columns=interval_start_utc,location,lmp&page_size=50"
```

## Example: CSV export

```bash theme={null}
curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.felixfusion.ai/v1/datasets/ercot_fuel_mix/query?return_format=csv&download=true"
```

## When to use path-based queries

The path-based route:

```text theme={null}
GET /v1/datasets/{dataset_id}/query/{filter_column_id}/{filter_value_path}
```

is useful when you want a simple stable filter encoded in the URL itself, such as a single location or category filter.