The response format is defined by the download scenarios described in the implementation guides, which are an integral part of the transparency platform’s manual of procedures.
- The response format is defined by the download scenarios described in the implementation guides, which are an integral part of the transparency platform’s manual of procedures.
Also in the response, time is always expressed in UTC.
System returns both partially and exactly matching data. The amount of returned data depends on the regulation article. For example, a query for one day of a weekly allocation will always return a whole week. Likewise, if the requested time interval in a query for a day-ahead allocation covers the last hours of one day and the first hours of the following day, the response will contain complete data for both days.
For the following regulation articles, the query response will contain data for a whole day (or a multiple of days, depending on the length of the requested time interval): Flow-based Allocations [11.1], Offered Transfer Capacities Implicit [11.1], Offered Transfer Capacities Explicit [11.1], Energy Prices [12.1.D], Total Capacity Already Allocated [12.1.C], Flow-based Allocations - Congestion Income [12.1.E], Implicit Allocations - Congestion Income [12.1.E], Auction Revenue [12.1.A], Use of Transfer Capacity [12.1.A], Transfer Capacities Allocated with Third Countries [12.1.H]. For the other regulation articles, the query response will contain data for the requested MTU or BTU period(s).
When querying for daily, weekly, monthly or yearly data, the time interval in the response corresponds to the day in the timezone for which the transparency platform publishes the data. For example: A query for article 12.1.d Energy Prices (day-ahead) for April 6 2016 in the Czech Republic will yield a response with a time interval starting at 2016-04-05T22:00Z and ending at 2016-04-06T22:00Z. In general, this is the timezone in which the area or border is geographically located. However, there can be exceptions to this rule due to regional arrangements for capacity allocations.
Curve type in response is A03 for all data items (see more details here).
When querying for border data (i.e. specifying in_Domain and out_Domain), the platform will export data only for one direction (import or export). To get the second direction, in_Domain and out_Domain values should be swapped and sent in a new request.
HTTP Return Codes for Unsuccessful Attempts:
| HTTP Code | Reason Code | Reason |
| 429 | - | Too many requests - max allowed 400 per minutes from eash unique IP |
| 200 | 999 | No matching data found |
| 400 | 999 | Invalid query attributes or parameters |
| 401 | Unauthorized. Missing or invalid security token |
Comments
0 comments
Article is closed for comments.