Central collection and publication of electricity generation, transportation and consumption data and information for the pan-European market.

1. Introduction

Data consumers may export data from the Transparency Platform data repository by submitting requests and receiving extracts via the ordinary MADES/ECP (IEC 62325-503) and web services (IEC 62325-504) channels. Further information on those channels is provided in the Manual of Procedures.

The Transparency Platform Data Extraction Process Implementation Guide explains the business context and provides the use case and process sequence.

The interface towards the Data Repository is asynchronous. Response time depends on current workload on the Transparency Platform and the size of the data you query. It may take several hours before you receive a response. If you require a fast response to your query, the synchronous restful API is recommended – be aware though that query size limits apply.

2. Authorization

Data consumers must be authorised before they can extract data from the Data Repository. To request access to the Data Repository, please send an email to transparency@entsoe.eu with "Data Repository access" in subject line. Indicate First Name and Last Name you provided during the registration on the Platform. The ENTSO-E Helpdesk will make their best efforts to respond to your request within 3 working days.

3. Request format

Data export requests towards the Data Repository are formatted using the Status Request Document. The format and rules can be found here. For the avoidance of any doubt, it should be noted that requests towards the Data Repository may not be submitted via https. Please refer to chapter 1 above for information on the available channels.

For more information about the Status Request Document please refer to EDI library.

The complete list of parameters can be found here.

Please note,

  • The ID of the status request document, i.e. the attribute mRID inside the document, must be unique for request you are submitting. The mRID will be used as a prefix to the export file name.
  • In order to ensure optimal usage of the platform without performence degradation, which could lead to failure of processing the requests, it's highly recomended to submit  <= ~930 requests/hour with Weekly and Monthly Time Period Interval 

For example: To extract data published under transparency regulation articles 15.1.a&b (planned unavailabilities and changes in actual availability of generation units) for the National Grid control area during the month of April 2016, a Status Request Document with the following content should be submitted:

<StatusRequest_MarketDocument xmlns="urn:iec62325.351:tc57wg16:451-5:statusrequestdocument:4:0">
    <sender_MarketParticipant.mRID codingScheme="A01">10V000000000008F</sender_MarketParticipant.mRID>
    <receiver_MarketParticipant.mRID codingScheme="A01">10X1001A1001A450</receiver_MarketParticipant.mRID>

4. Export data format

Rules and formats for the exports from the data repository can be found here. Please note though that for extracts from the data repository, the files are always packed into ZIP folder. One ZIP folder may contain multiple XML files for exports of transmission and production/generation outages. File naming convention for the ZIP folder with the extracted data is as follows: mRID.zip, where mRID is the Document ID of the submitted Status Request Document. The mRID can be used for matching requests with responses. Continuing the example in the previous chapter, the zip folder with the extracted data will be named SampleRequest.zip

5. Rejection of Request

Request is rejected when one or more of these conditions are met:

  • User is not allowed to use Data Repository

  • Document ID (mRID element) is not unique among user’s requests

  • Request does not contain all mandatory parameters

  • Request contains duplicate parameters

  • Parameters contain forbidden characters or letter case does not match

  • No data could be found

  • Requested data exceeds technical limit of 50 MB

System will return an Acknowledgement_MarketDocument with reasons of rejection.

6. Detailed guidelines and examples

For examples on how to query for each article under the transparency regulation, kindly refer to this chapter. There you will also find examples of the responses you may expect.