Docs
TenneT data connector
The TenneT Data APIs enable you to ingest real-time and historical energy market data from the Dutch Transmission System Operator (TSO), TenneT, directly into your Blockbax project. This tutorial focuses on integrating two key datasets:
- Settlement Prices: Imbalance prices per balancing time unit.
- Balance Delta: Operational volumes requested by TenneT via IGCC, PICASSO, aFRR, and incident reserves.
- If you are interested in ingesting one of the other Data APIs, please get in touch with us.
This connector is ideal for energy market analysts, grid operators, and data-driven energy applications.
Step 1: Send us an email
Send the following to support@blockbax.com:
Your TenneT API key. Follow the steps below to get your TenneT API key:
- Register yourself at TenneT API Developer Portal. After registration, you will need to wait for approval by TenneT.
- Once registered and approved you can generate a new API key for Production in TenneT’s API Developer Portal. Don’t forget to copy and save the API key after creation.
A Blockbax access key with only send measurements rights.
Your Blockbax project ID, found here:
That’s all, and to make it even easier, here is an example you can copy-paste:
Hi Blockbax Support,
Here is the information to enable the TenneT connector:
- TenneT API key: [ONE TIME LINK TO YOUR KEY]
- Blockbax API key: [ONE TIME LINK TO YOUR KEY]
- Blockbax project ID: [PROJECT ID]
- Data interval: Every 15 minutes
Please let me know when the integration is running.
Blockbax Support will come back to you as soon as possible when the connector is added to your project.
Step 2: Configure subject type
Create or edit a subject type where the data of TenneT can be ingested.
Add one or multiple of the following metrics.
Settlement Prices
Metric Name | Data Type | Unit | External ID |
---|---|---|---|
ISP | Number | tennet_isp | |
Incident Reserve Up | Text | tennet_incident_reserve_up | |
Incident Reserve Down | Text | tennet_incident_reserve_down | |
Dispatch Up | Number | €/MWh | tennet_dispatch_up |
Dispatch Down | Number | €/MWh | tennet_dispatch_down |
Shortage | Number | €/MWh | tennet_shortage |
Surplus | Number | €/MWh | tennet_surplus |
Regulation State | Number | tennet_regulation_state | |
Regulation Condition | Text | tennet_regulation_condition |
Balance Delta
Metric Name | Data Type | Unit | External ID |
---|---|---|---|
Sequence | Number | tennet_sequence | |
IGCC Contribution (Up) | Number | MAW | tennet_power_igcc_in |
IGCC Contribution (Down) | Number | MAW | tennet_power_igcc_out |
Activated Power Reg. (Up) | Number | MAW | tennet_power_afrr_in |
Activated Power Reg. (Down) | Number | MAW | tennet_power_afrr_out |
Activated Power Inc. (Up) | Number | MAW | tennet_power_mfrrda_in |
Activated Power Inc. (Down) | Number | MAW | tennet_power_mfrrda_out |
Picasso Contribution (Up) | Number | MAW | tennet_power_picasso_in |
Picasso Contribution (Down) | Number | MAW | tennet_power_picasso_out |
Price Dev. Highest Price (Up) | Number | €/MWh | tennet_max_upw_regulation_price |
Price Dev. Lowest Price (Down) | Number | €/MWh | tennet_min_downw_regulation_price |
Metric names can be arbitrarily chosen but the External ID should always be selected from the required format.
Step 3: Check if data is ingested
- Wait for an email from Blockbax Support that the integration is running.
- Check if the data is ingested correctly. Please contact us via support@blockbax.com if you find any issues.
Good luck with driving value from the TenneT data!