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
unit is CHF/kWh — this is a /api/v1 endpoint and preserves the
operators’ own unit. Multiply by 100 for Rappen.Parameters
Choosing products
products in the response tells you which tariff was used for each component.
To pick different ones, ask what is selectable:
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.
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:GET /api/v1/sgr/conformance reports how each operator’s dynamic-tariff API
scored against the SmartGridready specification on the last check.