Big Adjusted
RTE documentation
The RTE documentation is available here.
What this API collects
Reconstituted consumption and production curves for a delivery point, in two states:
- initial values, read from the detailed endpoint;
- updated values, published later by RTE when a curve is corrected. They are read from the updated data endpoint and overwrite what was collected before.
Insights configuration
Source
Create one source per EIC, as described in Source configuration.
| Property | Value |
|---|---|
| Source type | Rte |
| Meter number | The EIC code |
Variables
Each source can hold as many variables as there are combinations of state, data type, resolution and unit. A variable receives data only when its Mapping config matches the key rebuilt from the response — see The mapping config key.
| Property | Value |
|---|---|
| Name | Free text |
| Variable type | Basic |
| Mapping config | See Mapping config |
| Granularity | 10 minutes or 15 minutes, depending on the resolution of the data |
| Quantity type | Instant |
| Unit | Megawatt (MW) |
Mapping config
BIG-ADJUSTED_{state}_{dataType}_{resolution}_{unitName}
{state}
| Value | Meaning |
|---|---|
INITIAL |
The first values published for the day, read from the detailed endpoint. |
UPDATED |
Values corrected afterwards by RTE, read from the updated data endpoint. When a correction is published several times, the latest one wins. |
{dataType}
| Value | Meaning |
|---|---|
Z56 |
Consumption |
Z53 |
Production |
{resolution}
| Value | Applies to |
|---|---|
PT10M |
Data points timestamped before 2024-06-01T00:00:00Z |
PT15M |
Data points timestamped on or after 2024-06-01T00:00:00Z |
Important
The resolution follows the timestamp of the data, not the day it is collected. A recovery that reaches back across 2024-06-01 produces both resolutions in the same run, so both variables have to exist for the history to be complete.
{unitName}
| Value | Meaning |
|---|---|
MW |
Megawatt |
Examples
BIG-ADJUSTED_INITIAL_Z53_PT10M_MW
BIG-ADJUSTED_UPDATED_Z56_PT15M_MW
Collection schedule
The collection runs six times a day, in UTC. Two of these runs fall in the first slot of the day and collect the initial values before looking for corrections; the four others collect corrections only.
| Time (UTC) | BIG-ADJUSTED_INITIAL_* |
BIG-ADJUSTED_UPDATED_* |
|---|---|---|
| 00:30 | Yes | Yes |
| 07:30 | Yes | Yes |
| 08:15 | — | Yes |
| 14:30 | — | Yes |
| 16:00 | — | Yes |
| 17:00 | — | Yes |
Recovery behaviour
Big Adjusted differs from the other RTE collections here: it re-queries every day of the 31 day window on every run, whether the variables already hold data for those days or not.
Note
A correction that RTE publishes without exposing it on the updated data endpoint is therefore still picked up, but the flip side is a heavier collection and values that can be rewritten on any run. Treat the latest collected value as the reference rather than the first one.