Introduction
European power system data from TSOs, exchanges and transparency platforms.
The Grid API is a REST API for European power system data: production, consumption, prices, exchanges, capacities and balancing, collected from TSOs, exchanges and transparency platforms.
No API key is needed: every endpoint answers without one, at 30 requests per minute (Use without a key). A free key raises the limit to 240 per minute; Authentication says how to get one.
Two resources
Entities are the places that hold data: synchronous areas, countries, price zones, borders, interconnectors, substations, plants, units and portfolios, arranged as a tree. See Entities.
Timeseries are the data on an entity, identified by a name
(category.sub_category.definition[.component]) and a provider, the organisation that published
it. See Timeseries names.
Three steps
Every use of the API is the same three steps:
Discover an entity and the names of the timeseries on it, by walking the tree or by search.
Describe a timeseries: its definition, and for each provider its resolution, extent, publication latency and coverage. See Metadata.
Read its values for a time range. See Reading values.
How values are stored
Values are stored as published by the provider and are not filled, smoothed or estimated. Every
value carries the time it became known (knowledge_time), and a value that is published again is
kept as a new version. The as_of parameter on the values call selects which version is returned:
the latest, the one known at an instant, or a series of snapshots showing how it changed. Where a provider
fills a gap itself, the point says so in its annotation.
Notes on scope:
- Version history starts when the collection of a series starts (the earliest is 3 September 2026). Values before that are backfilled and have a single version.
publication_timein the metadata says whetherknowledge_timeisdeclaredby the provider ormeasuredas the time the value was observed to appear.- Clean series built by Rebase are published under the provider
rebase, with their inputs and method in the metadata.