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

# Price by the quarter-hour

> Any tariff as a time series — static or dynamic, one format for both.

A static tariff and a dynamic one look nothing alike in the source data: one is
a table of time windows, the other a feed of interval prices. For anything that
consumes prices — an energy management system, a load-shifting controller, a
cost model — that difference is pure friction.

`GET /api/v1/dsos/{dso_id}/timeseries` removes it. Every tariff comes back as a
series of intervals, whatever it is underneath.

## A day of prices

```bash theme={null}
curl "$TARIFF_API/api/v1/dsos/10117012345/timeseries?\
start=2026-02-03&end=2026-02-04&resolution=60"
```

```json theme={null}
{
  "vse_number": "10117012345",
  "resolution": "PT60M",
  "unit": "CHF_kWh",
  "products": {
    "2026": {
      "electricity": "AEW Energie Standard",
      "grid": "AEW Netz n7 Profil B NN",
      "feed_in": "AEW Rückliefervergütung (Wahltarif Abnahme ohne HKN)",
      "regional_fees": "AEW Classic Standard-Tarif Abgaben"
    }
  },
  "n": 24,
  "dynamic_components": [],
  "series": [
    { "start": "2026-02-03T00:00:00", "electricity": 0.1045, "grid": 0.057,
      "feed_in": 0.06, "total": 0.1615 }
  ]
}
```

> [!NOTE]
>
> `unit` is **CHF/kWh** — this is a `/api/v1` endpoint and preserves the
> operators' own unit. Multiply by 100 for Rappen.

## Parameters

| Parameter | Default | |
| - | - | - |
| `start`, `end` | today, tomorrow | ISO dates. Maximum range **92 days**. |
| `resolution` | `15` | Minutes: `15` or `60`. Anything else is a `422`. |
| `components` | all | Comma-separated: `electricity`, `grid`, `regional_fees`, `feed_in`. |
| `product` | the default per component | Repeatable; matches on part of the tariff name. |
| `format` | `json` | `csv` streams the same series as a download. |

## Choosing products

`products` in the response tells you which tariff was used for each component.
To pick different ones, ask what is selectable:

```bash theme={null}
curl "$TARIFF_API/api/v1/dsos/10117012345/timeseries/products?period=2026"
```

then filter by any part of a name — one filter may serve several components, and
components it does not match keep their default:

```bash theme={null}
curl "...?product=Naturstrom&product=Profil%20B"
```

> [!WARNING]
>
> A `product` filter that matches nothing is a `422`, not a silent fallback — with
> the available names in the error body. A filter that quietly failed would give
> you a plausible series for the wrong tariff, which is worse than an error.

## Static and dynamic in one series

Where the tariff is static, the operator's time windows (months, weekdays,
HT/NT) are expanded onto the grid. Where real dynamic prices have been captured
from an operator's own dynamic-tariff API, they **override** the static values
for those intervals, and the interval is marked `"source": "dynamic"`.

`dynamic_components` lists which components that happened for, so you can tell
at a glance whether a series is genuinely dynamic or a static tariff rendered as
one.

## The SmartGridready shape

If your consumer already speaks the SmartGridready / VSE dynamic-tariff V2
format, `GET /api/v1/dsos/{dso_id}/sgr-tariff` returns the same prices in that
response shape — one price interval per time window of the requested day, with
components `electricity`, `grid`, `regional_fees` and `feed_in`.

That lets an EMS use one format for every Swiss operator, dynamic or not,
including the \~480 that publish nothing dynamic at all.

```bash theme={null}
curl "$TARIFF_API/api/v1/dsos/10117012345/sgr-tariff?date=2026-02-03"
```

> [!NOTE]
>
> Responses carry `x-note`, `x-stage` and `x-dso` alongside the standard fields —
> the format has no place for provenance, and shipping prices without it would
> lose the one thing this dataset insists on.

## Captured dynamic prices

To see the raw captured intervals rather than a rendered series:

```bash theme={null}
curl "$TARIFF_API/api/v1/dynamic-prices?since=2026-02-01&limit=500"
```

And `GET /api/v1/sgr/conformance` reports how each operator's dynamic-tariff API
scored against the SmartGridready specification on the last check.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.