Get the forecast as parquet
Every request on these pages comes back as JSON. That's the default; the
Accept header picks another format. Parquet is the one to reach for when the
forecast goes straight into a dataframe, a warehouse or a lake: the same table,
typed and compressed, with nothing to parse.
This request forecasts a week of sales per city from the sample data:
Code
Ask for parquet with the Accept header:
Code
The button above sends the same header, and the playground shows the file as a table.
The formats
Accept | What comes back |
|---|---|
application/json (default) | One object, data, holding the table as one array per column. |
application/vnd.apache.parquet | The same table as a parquet file, one row per (series, time step). |
application/x-ndjson | One JSON record per series, one per line. |
application/vnd.msgpack | The same records as NDJSON, in MessagePack. |
application/x-tar | A tar archive of the parquet forecast and the input the model read. |
Anything else is rejected with 406 Not Acceptable, naming the formats above.
Parquet
One row per city and day, so 14 rows here. The columns are the ones the JSON
response carries in data: time and cutoff as UTC timestamps, lead_time
and span as ISO 8601 durations, then identifiers and targets as nested
structs, and auxiliary, empty for these requests. The first two rows, with
the quantiles rounded here:
| time | cutoff | lead_time | span | identifiers | targets |
|---|---|---|---|---|---|
| 2024-12-30 | 2024-12-29 | PT0S | P1D | {"city":"Lyon"} | {"sales":{"quantiles":{"0.1":51.63,"0.5":63.59,"0.9":74.74}}} |
| 2024-12-31 | 2024-12-29 | P1D | P1D | {"city":"Lyon"} | {"sales":{"quantiles":{"0.1":44.91,"0.5":56.02,"0.9":67.04}}} |
Read it with any parquet reader — pandas.read_parquet, polars.read_parquet,
DuckDB's read_parquet — and flatten the structs there if you want one column
per quantile.
NDJSON and MessagePack
One record per series instead of one row per step: each target's quantiles are arrays, one value per step. Trimmed to the first step:
Code
Times are written as steps from origin: the first forecast step is origin
plus first_step steps of frequency — here 2024-01-01 plus 364 days,
30 December.
The last line is not a series. It reports what the request used:
Code
The forecast and its input
application/x-tar returns two parquet files:
forecast.parquet— the same file the parquet format returns.materialization.parquet— the input rows as the model read them, after selection and roll-ups. Here that's one row per city and day — 728 rows — with each city's stores already summed:
| city | date | sales |
|---|---|---|
| Lyon | 2024-01-01 | 46 |
| Lyon | 2024-01-02 | 51 |
That's the series the model forecast from, so it's what to plot the forecast against, or what to check when a number looks off.

