Overview

Version information

Version : v1.9.4

URI scheme

Host : seffaflik.epias.com.tr
BasePath : /electricity-service
Schemes : HTTPS

Tags

  • consumption-data-controller

  • consumption-export-controller

  • dashboard-data-controller

  • generation-data-controller

  • generation-export-controller

  • main-data-controller

  • markets-ancillary-services-data-controller

  • markets-ancillary-services-export-controller

  • markets-bilateral-contracts-data-controller

  • markets-bilateral-contracts-export-controller

  • markets-dams-data-controller

  • markets-dams-export-controller

  • markets-data-controller

  • markets-dgp-data-controller

  • markets-dgp-export-controller

  • markets-export-controller

  • markets-gddk-data-controller

  • markets-gddk-export-controller

  • markets-general-data-data-controller

  • markets-general-data-export-controller

  • markets-gip-data-controller

  • markets-gip-export-controller

  • markets-gop-data-controller

  • markets-gop-export-controller

  • markets-imbalance-data-controller

  • markets-imbalance-export-controller

  • markets-vep-data-controller

  • markets-vep-export-controller

  • markets-yekg-data-controller

  • markets-yekg-export-controller

  • menu-controller

  • renewables-data-controller

  • renewables-export-controller

  • transmission-data-controller

  • transmission-export-controller

About Document

In this document, the definitions of Transparency Platform Electrical services and how to call these services are explained.

1. About Transparency Electrical Services

The Transparency Platform application is built on REST services. It accepts JSON and XML requests and returns JSON or XML response according to the incoming request.

All of the information you see in the user interface of the application is taken from these open services. It is possible to use the system with the applications you have without using this interface.

2. Adding Security Information To Requests

After deploying the security module on Exist Transparency project, if a user wants to fetch the data displayed on a logged-in web page, that user needs to add the necessary authentication information to the request. If not entered, you will see a redirecting response like this:

REQUEST_WITHOUT_TGT_EXAMPLE

Except for externally accessible services, security (authentication) information must be added to the requests in order to fetch data from the service endpoints. To do this, you must first obtain a TGT (ticket granting ticket) from, for testing environments https://giris-prp.epias.com.tr, and for production https://giris.epias.com.tr by sending a request with the relevant user information, as in the example below:

CAS_TGT_REQUEST_EXAMPLE

After that, you can enter this TGT in the relevant service endpoints like the image below. Time-to-live(TTL) for TGT is 2 hours, you can use the same TGT for different service endpoints for this TTL period.

REQUEST_WITH_TGT_EXAMPLE

3. Creating a Client

You can see this 5 minute tutorial to learn how to read this document and generate a request in Postman.

Service documentation is prepared with Swagger. By using appropriate swagger.json file, you can test and generate client codes suitable for the language you are using(for example, importing it to the Postman or using the Swagger Editor links below)

The date fields in all incoming and outgoing messages to the service are in ISO-8601 format. The format should be yyyy-MM-dd’T’HH:mm:ssXXX. Data in this platform are displayed in Turkish time zone(which is +0300, for older data consider older daylight savings rules) Example date value: 2023-11-14T17:30:00+03:00
Example ISO8601 Parser Java 8
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;

public class DateUtil
{

    public static Date fromISO8601Date(String v)
    {
        if (null == v) return null;
        SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssXXX");
        try
        {
            return sdf.parse(v);
        } catch (ParseException e)
        {
            throw new RuntimeException(e);
        }
    }

    public static String toISO8601Date(Date v)
    {
        if (null == v) return null;
        SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssXXX");
        return sdf.format(v);
    }
}
When it is desired to receive the returned data in the services with pages, the paging data should be sent to the service as a parameter. You can examine how to make a pagination request through the example below.
Example Pagination Request
 "page": {
   "number":1, // Page number
   "size":20,// Row count on one page.
   "sort":{
     "direction":"ASC",// data sorting direction. ASC ya da DESC.
     "field":"date" // field name for sorting. it is predetermined by each of the service endpoint
   },
   "total":0 // not required for request, this field is for returning total data count from server.
 }

4. Service Details

From this section, you can access information about service call details according to their categories.

5. Paths

5.1. Consumer Quantity Listing Service

POST /v1/consumption/data/consumer-quantity

5.1.1. Description

The division of consumer numbers on a provincial basis according to consumer type and consumer profile groups is shown on a monthly basis.

5.1.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.1.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.1.4. Consumes

  • application/json

  • application/xml

5.1.5. Produces

  • application/json

  • application/xml

5.1.6. Tags

  • consumption-data-controller

5.2. Profile Group Listing Service

GET /v1/consumption/data/consumer-sector-list

5.2.1. Description

Profile Group Listing Service for the Consumer Information pages

5.2.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.2.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.2.4. Produces

  • application/json

  • application/xml

5.2.5. Tags

  • consumption-data-controller

5.3. Consumption Quantity Listing Service

POST /v1/consumption/data/consumption-quantity

5.3.1. Description

The breakdown of Consumption Quantities by consumer type and consumer profile groups is shown monthly based on province.

5.3.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.3.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.3.4. Consumes

  • application/json

  • application/xml

5.3.5. Produces

  • application/json

  • application/xml

5.3.6. Tags

  • consumption-data-controller

5.4. Demand Forecast Service,

POST /v1/consumption/data/demand-forecast

5.4.1. Description

Demand Forecast Service,

5.4.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.4.3. Responses

HTTP Code Description Schema

200

successful operation

5.4.4. Consumes

  • application/json

  • application/xml

5.4.5. Produces

  • application/json

  • application/xml

5.4.6. Tags

  • consumption-data-controller

5.5. Distribution Region

GET /v1/consumption/data/distribution-region

5.5.1. Description

Distribution Region

5.5.2. Responses

HTTP Code Description Schema

200

successful operation

5.5.3. Produces

  • application/json

  • application/xml

5.5.4. Tags

  • consumption-data-controller

5.6. City, District Eligible Customer Number Listing Service

POST /v1/consumption/data/eligible-consumer-count

5.6.1. Description

The number of meters with eligible costumer usage type based on district and profile subscriber group. Past district names may be included in the shared district information. It is kindly requested to pay attention to this issue while making the analysis.

5.6.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.6.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.6.4. Consumes

  • application/json

  • application/xml

5.6.5. Produces

  • application/json

  • application/xml

5.6.6. Tags

  • consumption-data-controller

5.7. Eligible Customer Quantity Listing Service

POST /v1/consumption/data/eligible-consumer-quantity

5.7.1. Description

The number of meters with eligible costumer usage type based on district and profile subscriber group

5.7.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.7.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.7.4. Consumes

  • application/json

  • application/xml

5.7.5. Produces

  • application/json

  • application/xml

5.7.6. Tags

  • consumption-data-controller

5.8. Service For Getting Distribution Companies

GET /v1/consumption/data/get-distribution-companies

5.8.1. Description

Service For Getting Distribution Companies

5.8.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.8.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.8.4. Produces

  • application/json

  • application/xml

5.8.5. Tags

  • consumption-data-controller

5.9. Load Forecast Plan Data Listing Service

POST /v1/consumption/data/load-estimation-plan

5.9.1. Description

Total hourly power consumption forecast plans for the next day.

5.9.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.9.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.9.4. Consumes

  • application/json

  • application/xml

5.9.5. Produces

  • application/json

  • application/xml

5.9.6. Tags

  • consumption-data-controller

5.10. Main Tariff Group

GET /v1/consumption/data/main-tariff-group-list

5.10.1. Description

Main Tariff Group Service.

5.10.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.10.3. Responses

HTTP Code Description Schema

200

Operation successful

< MainTariffGroup > array

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.10.4. Produces

  • application/json

  • application/xml

5.10.5. Tags

  • consumption-data-controller

5.11. Meter Count Data Listing Service

POST /v1/consumption/data/meter-count

5.11.1. Description

It is the number of meters data announced for the period following the current period.

5.11.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.11.3. Responses

HTTP Code Description Schema

200

successful operation

5.11.4. Consumes

  • application/json

  • application/xml

5.11.5. Produces

  • application/json

  • application/xml

5.11.6. Tags

  • consumption-data-controller

5.12. Monthly Index Listing Service

POST /v1/consumption/data/monthly-index

5.12.1. Description

The data set regarding the value calculated by using Market Clearing Price (MCP), Negative System Imbalance Price, Renewable Energy Support Mechanism Unit Cost, National Tariff Unit Cost, Withdrawal Quantities on the basis of settlement period for customers registered in the Market Management System. Reference Index is 100.

5.12.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.12.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.12.4. Consumes

  • application/json

  • application/xml

5.12.5. Produces

  • application/json

  • application/xml

5.12.6. Tags

  • consumption-data-controller

5.13. Multiple Factor Data Listing Service

POST /v1/consumption/data/multiple-factor

5.13.1. Description

The data set regarding the value used for profiling of meters that cannot be read on a settlement period basis.

5.13.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.13.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.13.4. Consumes

  • application/json

  • application/xml

5.13.5. Produces

  • application/json

  • application/xml

5.13.6. Tags

  • consumption-data-controller

5.14. Distribution Firms Listing Service

POST /v1/consumption/data/multiple-factor-distribution

5.14.1. Description

Distribution Firms Listing Service

5.14.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.14.3. Responses

HTTP Code Description Schema

200

Operation successful

< Distribution > array

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.14.4. Produces

  • application/json

  • application/xml

5.14.5. Tags

  • consumption-data-controller

5.15. Meter Reading Type Listing Service

GET /v1/consumption/data/multiple-factor-meter-reading-type

5.15.1. Description

Meter Reading Type Listing Service

5.15.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.15.3. Responses

HTTP Code Description Schema

200

Operation successful

< MeterReadingType > array

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.15.4. Produces

  • application/json

  • application/xml

5.15.5. Tags

  • consumption-data-controller

5.16. Profile Group Listing Service

POST /v1/consumption/data/multiple-factor-profile-group

5.16.1. Description

If the distributionId field is provided, it will list the valid Profile Group according to the distribution company/organization ID information for the relevant period, if left empty, it will list all Profile Group.

5.16.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.16.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.16.4. Produces

  • application/json

  • application/xml

5.16.5. Tags

  • consumption-data-controller

5.17. Percentage of Consumption Information Data Listing Service

POST /v1/consumption/data/percentage-consumption-info

5.17.1. Description

The data set regarding the percentage of actual consumption by city and customer profile group.

5.17.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.17.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.17.4. Consumes

  • application/json

  • application/xml

5.17.5. Produces

  • application/json

  • application/xml

5.17.6. Tags

  • consumption-data-controller

5.18. Planned Failure Information Listing Service

POST /v1/consumption/data/planned-power-outage-info

5.18.1. Description

This is the screen where information about the planned outage is presented.

5.18.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.18.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.18.4. Consumes

  • application/json

  • application/xml

5.18.5. Produces

  • application/json

  • application/xml

5.18.6. Tags

  • consumption-data-controller

5.19. Customer Profile Group Service

POST /v1/consumption/data/profile-subscription-group-list

5.19.1. Description

Customer Profile Group Service

5.19.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.19.3. Responses

HTTP Code Description Schema

200

Operation successful

< string > array

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.19.4. Consumes

  • application/json

  • application/xml

5.19.5. Produces

  • application/json

  • application/xml

5.19.6. Tags

  • consumption-data-controller

5.20. Real Time Consumption Data Listing Service

POST /v1/consumption/data/realtime-consumption

5.20.1. Description

It is the data that shows the instantaneous consumption value on an hourly basis. Real-Time Consumption data is published 2 hours behind.

5.20.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.20.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.20.4. Consumes

  • application/json

  • application/xml

5.20.5. Produces

  • application/json

  • application/xml

5.20.6. Tags

  • consumption-data-controller

5.21. Eligible Customer Count Listing Service

POST /v1/consumption/data/st-adedi

5.21.1. Description

The number of meters with eligible costumer usage type

5.21.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.21.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.21.4. Consumes

  • application/json

  • application/xml

5.21.5. Produces

  • application/json

  • application/xml

5.21.6. Tags

  • consumption-data-controller

5.22. Eligible Customer Withdrawal Quantity Data Listing Service

POST /v1/consumption/data/st-uecm

5.22.1. Description

The data set regarding total hourly energy withdrawal quantity of eligible customers

5.22.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.22.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.22.4. Consumes

  • application/json

  • application/xml

5.22.5. Produces

  • application/json

  • application/xml

5.22.6. Tags

  • consumption-data-controller

5.23. Withdrawal Quantity Data Listing Service

POST /v1/consumption/data/uecm

5.23.1. Description

The data set regarding total hourly energy withdrawal quantity of withdrawal units.

5.23.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.23.3. Responses

HTTP Code Description Schema

200

successful operation

5.23.4. Consumes

  • application/json

  • application/xml

5.23.5. Produces

  • application/json

  • application/xml

5.23.6. Tags

  • consumption-data-controller

5.24. Unplanned Failure Information Listing Service

POST /v1/consumption/data/unplanned-power-outage-info

5.24.1. Description

This is the screen where unplanned outage are presented.

5.24.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.24.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.24.4. Consumes

  • application/json

  • application/xml

5.24.5. Produces

  • application/json

  • application/xml

5.24.6. Tags

  • consumption-data-controller

5.25. Withdrawal Quantity Under Supply Liability Data Listing Service

POST /v1/consumption/data/withdrawal-quantity-under-supply-liability

5.25.1. Description

The data set regarding total energy withdrawal quantity under supply liability of withdrawal units. If YEKDEM revenue is more than the total price of YEK in an invoicing period, the calculation is made in accordance with the fourth paragraph of Article 13 of the Regulation on Certification and Support of Renewable Energy Resources, and the unit price applied to suppliers for all sales except the sales of the Authorized Supply Companies within the scope of K1 is 0 TL/MWh.

5.25.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.25.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.25.4. Consumes

  • application/json

  • application/xml

5.25.5. Produces

  • application/json

  • application/xml

5.25.6. Tags

  • consumption-data-controller

5.26. Consumer Quantity Export Service

POST /v1/consumption/export/consumer-quantity

5.26.1. Description

The division of consumer numbers on a provincial basis according to consumer type and consumer profile groups is shown on a monthly basis. Exports Consumer Quantity datas as XLSX, CSV or PDF formats.

5.26.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.26.3. Responses

HTTP Code Description Schema

200

successful operation

5.26.4. Consumes

  • application/json

  • application/xml

5.26.5. Produces

  • application/json

  • application/xml

5.26.6. Tags

  • consumption-export-controller

5.27. Consumption Quantity Export Service

POST /v1/consumption/export/consumption-quantity

5.27.1. Description

The breakdown of Consumption Quantities by consumer type and consumer profile groups is shown monthly based on province. Exports Consumption Quantity datas as XLSX, CSV or PDF formats.

5.27.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.27.3. Responses

HTTP Code Description Schema

200

successful operation

5.27.4. Consumes

  • application/json

  • application/xml

5.27.5. Produces

  • application/json

  • application/xml

5.27.6. Tags

  • consumption-export-controller

5.28. Demand Forecest Data Export Service

POST /v1/consumption/export/demand-forecast-export

5.28.1. Description

Demand Forecast Service Which Can Be Exported

5.28.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.28.3. Responses

HTTP Code Description Schema

200

successful operation

5.28.4. Consumes

  • application/json

  • application/xml

5.28.5. Produces

  • application/json

  • application/xml

5.28.6. Tags

  • consumption-export-controller

5.29. City, District Eligible Customer Number Export Service

POST /v1/consumption/export/eligible-consumer-count

5.29.1. Description

The number of meters with eligible costumer usage type based on district and profile subscriber group. Past district names may be included in the shared district information. It is kindly requested to pay attention to this issue while making the analysis. Exports City, District Eligible Customer Number datas as XLSX, CSV or PDF formats.

5.29.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.29.3. Responses

HTTP Code Description Schema

200

successful operation

5.29.4. Consumes

  • application/json

  • application/xml

5.29.5. Produces

  • application/json

  • application/xml

5.29.6. Tags

  • consumption-export-controller

5.30. Eligible Customer Quantity Export Service

POST /v1/consumption/export/eligible-consumer-quantity

5.30.1. Description

The number of meters with eligible costumer usage type based on district and profile subscriber group. Exports Eligible Customer Quantity datas as XLSX, CSV or PDF formats.

5.30.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.30.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.30.4. Consumes

  • application/json

  • application/xml

5.30.5. Produces

  • application/json

  • application/xml

5.30.6. Tags

  • consumption-export-controller

5.31. Load Forecast Plan Export Service

POST /v1/consumption/export/load-estimation-plan

5.31.1. Description

Total hourly power consumption forecast plans for the next day. Exports Load Forecast Plan datas as XLSX, CSV or PDF formats.

5.31.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.31.3. Responses

HTTP Code Description Schema

200

successful operation

5.31.4. Consumes

  • application/json

  • application/xml

5.31.5. Produces

  • application/json

  • application/xml

5.31.6. Tags

  • consumption-export-controller

5.32. Meter Count Export Service

POST /v1/consumption/export/meter-count-export

5.32.1. Description

It is the number of meters data announced for the period following the current period. Exports Meter Count datas as XLSX, CSV or PDF formats.

5.32.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.32.3. Responses

HTTP Code Description Schema

200

successful operation

5.32.4. Consumes

  • application/json

  • application/xml

5.32.5. Produces

  • application/json

  • application/xml

5.32.6. Tags

  • consumption-export-controller

5.33. Monthly Index Export Service

POST /v1/consumption/export/monthly-index

5.33.1. Description

The data set regarding the value calculated by using Market Clearing Price (MCP), Negative System Imbalance Price, Renewable Energy Support Mechanism Unit Cost, National Tariff Unit Cost, Withdrawal Quantities on the basis of settlement period for customers registered in the Market Management System. Reference Index is 100. Exports Monthly Index datas as XLSX, CSV or PDF formats.

5.33.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.33.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.33.4. Consumes

  • application/json

  • application/xml

5.33.5. Produces

  • application/json

  • application/xml

5.33.6. Tags

  • consumption-export-controller

5.34. Multiple Factor Export Service

POST /v1/consumption/export/multiple-factor

5.34.1. Description

The data set regarding the value used for profiling of meters that cannot be read on a settlement period basis.Exports Multiple Factor datas as XLSX, CSV or PDF formats.

5.34.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.34.3. Responses

HTTP Code Description Schema

200

successful operation

5.34.4. Consumes

  • application/json

  • application/xml

5.34.5. Produces

  • application/json

  • application/xml

5.34.6. Tags

  • consumption-export-controller

5.35. Percentage of Consumption Information Export Service

POST /v1/consumption/export/percentage-consumption-info

5.35.1. Description

The data set regarding the percentage of actual consumption by city and customer profile group. Exports Percentage of Consumption Information datas as XLSX, CSV or PDF formats.

5.35.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.35.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.35.4. Consumes

  • application/json

  • application/xml

5.35.5. Produces

  • application/json

  • application/xml

5.35.6. Tags

  • consumption-export-controller

5.36. Planned Failure Information Export Service

POST /v1/consumption/export/planned-power-outage-info

5.36.1. Description

This is the screen where information about the planned outage is presented. Exports Planned Failure Information datas as XLSX, CSV or PDF formats.

5.36.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.36.3. Responses

HTTP Code Description Schema

200

successful operation

5.36.4. Consumes

  • application/json

  • application/xml

5.36.5. Produces

  • application/json

  • application/xml

5.36.6. Tags

  • consumption-export-controller

5.37. Real Time Consumption Export Service

POST /v1/consumption/export/realtime-consumption

5.37.1. Description

It is the data that shows the instantaneous consumption value on an hourly basis. Real-Time Consumption data is published 2 hours behind.

5.37.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.37.3. Responses

HTTP Code Description Schema

200

successful operation

5.37.4. Consumes

  • application/json

  • application/xml

5.37.5. Produces

  • application/json

  • application/xml

5.37.6. Tags

  • consumption-export-controller

5.38. Eligible Customer Count Export Service

POST /v1/consumption/export/st-adedi

5.38.1. Description

The number of meters with eligible costumer usage type. Exports Eligible Customer Count datas as XLSX, CSV or PDF formats.

5.38.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.38.3. Responses

HTTP Code Description Schema

200

successful operation

5.38.4. Consumes

  • application/json

  • application/xml

5.38.5. Produces

  • application/json

  • application/xml

5.38.6. Tags

  • consumption-export-controller

5.39. Eligible Customer Withdrawal Quantity Export Service

POST /v1/consumption/export/st-uecm

5.39.1. Description

The data set regarding total hourly energy withdrawal quantity of eligible customers. Exports Eligible Customer Withdrawal Quantity datas as XLSX, CSV or PDF formats.

5.39.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.39.3. Responses

HTTP Code Description Schema

200

successful operation

5.39.4. Consumes

  • application/json

  • application/xml

5.39.5. Produces

  • application/json

  • application/xml

5.39.6. Tags

  • consumption-export-controller

5.40. Withdrawal Quantity Export Service

POST /v1/consumption/export/uecm-export

5.40.1. Description

The data set regarding total hourly energy withdrawal quantity of withdrawal units. Exports Withdrawal Quantity datas as XLSX, CSV or PDF formats.

5.40.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.40.3. Responses

HTTP Code Description Schema

200

successful operation

5.40.4. Consumes

  • application/json

  • application/xml

5.40.5. Produces

  • application/json

  • application/xml

5.40.6. Tags

  • consumption-export-controller

5.41. Unplanned Failure Information Export Service

POST /v1/consumption/export/unplanned-power-outage-info

5.41.1. Description

This is the screen where unplanned outage are presented. Exports Unplanned Failure Information datas as XLSX, CSV or PDF formats.

5.41.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.41.3. Responses

HTTP Code Description Schema

200

successful operation

5.41.4. Consumes

  • application/json

  • application/xml

5.41.5. Produces

  • application/json

  • application/xml

5.41.6. Tags

  • consumption-export-controller

5.42. Withdrawal Quantity Under Supply Liability Export Service

POST /v1/consumption/export/withdrawal-quantity-under-supply-liability

5.42.1. Description

The data set regarding total energy withdrawal quantity under supply liability of withdrawal units. If YEKDEM revenue is more than the total price of YEK in an invoicing period, the calculation is made in accordance with the fourth paragraph of Article 13 of the Regulation on Certification and Support of Renewable Energy Resources, and the unit price applied to suppliers for all sales except the sales of the Authorized Supply Companies within the scope of K1 is 0 TL/MWh. Exports Withdrawal Quantity Under Supply Liability datas as XLSX, CSV or PDF formats.

5.42.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.42.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.42.4. Consumes

  • application/json

  • application/xml

5.42.5. Produces

  • application/json

  • application/xml

5.42.6. Tags

  • consumption-export-controller

5.43. Active Fullness Data Listing Service

POST /v1/dams/data/active-fullness

5.43.1. Description

The percentage of volume between the maximum and minimum operating levels of a dam. Formula: Active Occupancy= [( Volume Corresponding to the Level on the Relevant Date - Minimum Volume ) / ( Maximum Volume - Minimum Volume )] *100. Data is finalized as of 17:00. Dam data is provided daily. There is no retrospective data.

5.43.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.43.3. Responses

HTTP Code Description Schema

200

successful operation

5.43.4. Consumes

  • application/json

  • application/xml

5.43.5. Produces

  • application/json

  • application/xml

5.43.6. Tags

  • markets-dams-data-controller

5.44. Active Volume Data Listing Service

POST /v1/dams/data/active-volume

5.44.1. Description

The volume between the minimum volume and minimum operating levels of a dam at the relevant date. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data.

5.44.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.44.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.44.4. Consumes

  • application/json

  • application/xml

5.44.5. Produces

  • application/json

  • application/xml

5.44.6. Tags

  • markets-dams-data-controller

5.45. Service that returns the basin list.

GET /v1/dams/data/basin-list

5.45.1. Description

Service that returns the basin list.

5.45.2. Responses

HTTP Code Description Schema

200

successful operation

< string > array

5.45.3. Produces

  • application/json

  • application/xml

5.45.4. Tags

  • markets-dams-data-controller

5.46. Daily Kot Data Listing Service

POST /v1/dams/data/daily-kot

5.46.1. Description

Indicates the water height of the dam on the relevant day. The data is finalized as of 5 pm. Dam data is provided daily. There is no retrospective data.

5.46.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.46.3. Responses

HTTP Code Description Schema

200

successful operation

5.46.4. Consumes

  • application/json

  • application/xml

5.46.5. Produces

  • application/json

  • application/xml

5.46.6. Tags

  • markets-dams-data-controller

5.47. Daily Volume Data Listing Service

POST /v1/dams/data/daily-volume

5.47.1. Description

The volume corresponding to the level of a dam at the relevant date. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data.

5.47.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.47.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.47.4. Consumes

  • application/json

  • application/xml

5.47.5. Produces

  • application/json

  • application/xml

5.47.6. Tags

  • markets-dams-data-controller

5.48. Kot Data Listing Service

POST /v1/dams/data/dam-kot

5.48.1. Description

Indicates the minimum and maximum water level of the dam.

5.48.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.48.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.48.4. Consumes

  • application/json

  • application/xml

5.48.5. Produces

  • application/json

  • application/xml

5.48.6. Tags

  • markets-dams-data-controller

5.49. The service that returns the list of Dams with the name of the basin.

POST /v1/dams/data/dam-list

5.49.1. Description

The service that returns the list of Dams with the name of the basin.

5.49.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.49.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.49.4. Consumes

  • application/json

  • application/xml

5.49.5. Produces

  • application/json

  • application/xml

5.49.6. Tags

  • markets-dams-data-controller

5.50. Volume Data Listing Service

POST /v1/dams/data/dam-volume

5.50.1. Description

It shows the maximum and minimum volume level of the relevant dam.

5.50.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.50.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.50.4. Consumes

  • application/json

  • application/xml

5.50.5. Produces

  • application/json

  • application/xml

5.50.6. Tags

  • markets-dams-data-controller

5.51. Flow Rate and Installed Power Data Listing Service

POST /v1/dams/data/flow-rate-and-installed-power

5.51.1. Description

It shows the amount of water passing through the unit in the relevant dam and the installed power of the dam.

5.51.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.51.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.51.4. Consumes

  • application/json

  • application/xml

5.51.5. Produces

  • application/json

  • application/xml

5.51.6. Tags

  • markets-dams-data-controller

5.52. Water Energy Provision Data Listing Service

POST /v1/dams/data/water-energy-provision

5.52.1. Description

The energy equivalent of Mwh in the dam. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data.

5.52.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.52.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.52.4. Consumes

  • application/json

  • application/xml

5.52.5. Produces

  • application/json

  • application/xml

5.52.6. Tags

  • markets-dams-data-controller

5.53. Active Fullness Export Service

POST /v1/dams/export/active-fullness

5.53.1. Description

The percentage of volume between the maximum and minimum operating levels of a dam. Formula: Active Occupancy= [( Volume Corresponding to the Level on the Relevant Date - Minimum Volume ) / ( Maximum Volume - Minimum Volume )] *100. Data is finalized as of 17:00. Dam data is provided daily. There is no retrospective data. Exports Active Fullness datas as XLSX, CSV or PDF formats.

5.53.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.53.3. Responses

HTTP Code Description Schema

200

successful operation

5.53.4. Consumes

  • application/json

  • application/xml

5.53.5. Produces

  • application/json

  • application/xml

5.53.6. Tags

  • markets-dams-export-controller

5.54. Active Volume Export Service

POST /v1/dams/export/active-volume

5.54.1. Description

The volume between the minimum volume and minimum operating levels of a dam at the relevant date. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data. Exports Active Volume datas as XLSX, CSV or PDF formats.

5.54.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.54.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.54.4. Consumes

  • application/json

  • application/xml

5.54.5. Produces

  • application/json

  • application/xml

5.54.6. Tags

  • markets-dams-export-controller

5.55. Daily Kot Export Service

POST /v1/dams/export/daily-kot

5.55.1. Description

Indicates the water height of the dam on the relevant day. The data is finalized as of 5 pm. Dam data is provided daily. There is no retrospective data. Exports Daily Kot datas as XLSX, CSV or PDF formats.

5.55.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.55.3. Responses

HTTP Code Description Schema

200

successful operation

5.55.4. Consumes

  • application/json

  • application/xml

5.55.5. Produces

  • application/json

  • application/xml

5.55.6. Tags

  • markets-dams-export-controller

5.56. Daily Volume Export Service

POST /v1/dams/export/daily-volume

5.56.1. Description

The volume corresponding to the level of a dam at the relevant date. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data. Exports Daily Volume datas as XLSX, CSV or PDF formats.

5.56.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.56.3. Responses

HTTP Code Description Schema

200

successful operation

5.56.4. Consumes

  • application/json

  • application/xml

5.56.5. Produces

  • application/json

  • application/xml

5.56.6. Tags

  • markets-dams-export-controller

5.57. Kot Export Service

POST /v1/dams/export/dam-kot

5.57.1. Description

Indicates the minimum and maximum water level of the dam. Exports Kot datas as XLSX, CSV or PDF formats.

5.57.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.57.3. Responses

HTTP Code Description Schema

200

successful operation

5.57.4. Consumes

  • application/json

  • application/xml

5.57.5. Produces

  • application/json

  • application/xml

5.57.6. Tags

  • markets-dams-export-controller

5.58. Volume Export Service

POST /v1/dams/export/dam-volume

5.58.1. Description

It shows the maximum and minimum volume level of the relevant dam. Exports Volume datas as XLSX, CSV or PDF formats.

5.58.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.58.3. Responses

HTTP Code Description Schema

200

successful operation

5.58.4. Consumes

  • application/json

  • application/xml

5.58.5. Produces

  • application/json

  • application/xml

5.58.6. Tags

  • markets-dams-export-controller

5.59. Flow Rate and Installed Power Export Service

POST /v1/dams/export/flow-rate-and-installed-power

5.59.1. Description

It shows the amount of water passing through the unit in the relevant dam and the installed power of the dam. Exports Flow Rate and Installed Power datas as XLSX, CSV or PDF formats.

5.59.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.59.3. Responses

HTTP Code Description Schema

200

successful operation

5.59.4. Consumes

  • application/json

  • application/xml

5.59.5. Produces

  • application/json

  • application/xml

5.59.6. Tags

  • markets-dams-export-controller

5.60. Water Energy Provision Export Service

POST /v1/dams/export/water-energy-provision

5.60.1. Description

The energy equivalent of Mwh in the dam. Data is finalized at 17:00. Dam data is provided daily. There is no retrospective data. Exports Water Energy Provision datas as XLSX, CSV or PDF formats.

5.60.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.60.3. Responses

HTTP Code Description Schema

200

successful operation

5.60.4. Consumes

  • application/json

  • application/xml

5.60.5. Produces

  • application/json

  • application/xml

5.60.6. Tags

  • markets-dams-export-controller

5.61. Transparency dashboard balancing power market data service

GET /v1/dashboard/balancing-power-market

5.61.1. Description

Transparency dashboard balancing power market data service

5.61.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.61.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.61.4. Produces

  • application/json

  • application/xml

5.61.5. Tags

  • dashboard-data-controller

5.62. Transparency dashboard day ahead market data service

GET /v1/dashboard/day-ahead-market

5.62.1. Description

Transparency dashboard day ahead market data service

5.62.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.62.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.62.4. Produces

  • application/json

  • application/xml

5.62.5. Tags

  • dashboard-data-controller

5.63. Transparency dashboard intra day data service

GET /v1/dashboard/intra-day-market

5.63.1. Description

Transparency dashboard intra day data service

5.63.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.63.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.63.4. Produces

  • application/json

  • application/xml

5.63.5. Tags

  • dashboard-data-controller

5.64. Transparency dashboard market message system service

GET /v1/dashboard/market-message-system

5.64.1. Description

Transparency dashboard market message system service

5.64.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.64.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.64.4. Produces

  • application/json

  • application/xml

5.64.5. Tags

  • dashboard-data-controller

5.65. Transparency dashboard realtime consumption data service

GET /v1/dashboard/realtime-consumption

5.65.1. Description

Transparency dashboard realtime consumption data service

5.65.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.65.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.65.4. Produces

  • application/json

  • application/xml

5.65.5. Tags

  • dashboard-data-controller

5.66. Transparency dashboard realtime generation data service

GET /v1/dashboard/realtime-generation

5.66.1. Description

Transparency dashboard realtime generation data service

5.66.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.66.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.66.4. Produces

  • application/json

  • application/xml

5.66.5. Tags

  • dashboard-data-controller

5.67. Transparency dashboard spot gaz market data service

GET /v1/dashboard/spot-gas-market

5.67.1. Description

Transparency dashboard spot gaz market data service

5.67.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.67.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.67.4. Produces

  • application/json

  • application/xml

5.67.5. Tags

  • dashboard-data-controller

5.68. Transparency Dashboard Weighted Average Price Data Service

GET /v1/dashboard/weighted-average-price

5.68.1. Description

Transparency Dashboard Weighted Average Price Data Service

5.68.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.68.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.68.4. Produces

  • application/json

  • application/xml

5.68.5. Tags

  • dashboard-data-controller

5.69. Available Installed Capacity (AIC) Data Listing Service

POST /v1/generation/data/aic

5.69.1. Description

Available Installed Capacity : The active power capacity that a generation unit can provide to the system.

5.69.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.69.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.69.4. Consumes

  • application/json

  • application/xml

5.69.5. Produces

  • application/json

  • application/xml

5.69.6. Tags

  • generation-data-controller

5.70. Final Daily Production Program (FDPP) Data Listing Service

POST /v1/generation/data/dpp

5.70.1. Description

Final day-ahead generation/consumption schedule (FDGS): The generation or consumption values which a settlement feed in-feed out unit anticipates to realize in the following day and notifies the System Operator at the opening of the balancing power market, depending on the obligations of the balancing responsible unit that it is a member of and the result of day-ahead balancing.

5.70.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.70.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.70.4. Consumes

  • application/json

  • application/xml

5.70.5. Produces

  • application/json

  • application/xml

5.70.6. Tags

  • generation-data-controller

5.71. ${VALUE_KGUP_ILK_VERSION_DATA}

POST /v1/generation/data/dpp-first-version

5.71.1. Description

${NOTES_KGUP_ILK_VERSION_DATA}

5.71.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.71.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.71.4. Consumes

  • application/json

  • application/xml

5.71.5. Produces

  • application/json

  • application/xml

5.71.6. Tags

  • generation-data-controller

5.72. Injection Quantity List Service

POST /v1/generation/data/injection-quantity

5.72.1. Description

Settlement Based Power Generation: The total value of the resource based electricity amount given to the system hourly by the settlement units within a settlement period.

5.72.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.72.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.72.4. Consumes

  • application/json

  • application/xml

5.72.5. Produces

  • application/json

  • application/xml

5.72.6. Tags

  • generation-data-controller

5.73. Injection Quantity Powerplant Listing Service

GET /v1/generation/data/injection-quantity-powerplant-list

5.73.1. Description

Injection Quantity Powerplant Listing Service

5.73.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.73.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.73.4. Produces

  • application/json

  • application/xml

5.73.5. Tags

  • generation-data-controller

5.74. Licenced Power Plant Investments Data Listing Service

POST /v1/generation/data/licensed-powerplant-investment-list

5.74.1. Description

It is the monthly list of electricity generation facilities that are pre-approved and put into operation by the General Directorate of Energy Affairs. It is the monthly list of electricity generation facilities.

5.74.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.74.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.74.4. Produces

  • application/json

  • application/xml

5.74.5. Tags

  • generation-data-controller

5.75. Organization Listing Service

POST /v1/generation/data/organization-list

5.75.1. Description

Organization Listing Service

5.75.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.75.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.75.4. Consumes

  • application/json

  • application/xml

5.75.5. Produces

  • application/json

  • application/xml

5.75.6. Tags

  • generation-data-controller

5.76. Power plant information listing service

GET /v1/generation/data/powerplant-list

5.76.1. Description

Power plant Information Listing Service for TEIAS Systems. The power plant information returned(i.e: power plant id) as a result of this service consists of data received from TEIAS systems.

5.76.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.76.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.76.4. Produces

  • application/json

  • application/xml

5.76.5. Tags

  • generation-data-controller

5.77. Real-Time Generation Data Listing Service

POST /v1/generation/data/realtime-generation

5.77.1. Description

Real time generation: The display of hourly generation values of electricity generation plants on a resource basis. For power plant specific generation data, latest data shown is a day before current date. Requests for the current date’s power plant specific generation data will return a bad request(HTTP 400)

5.77.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.77.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.77.4. Consumes

  • application/json

  • application/xml

5.77.5. Produces

  • application/json

  • application/xml

5.77.6. Tags

  • generation-data-controller

5.78. Region Listing Service

GET /v1/generation/data/region-list

5.78.1. Description

Region Listing Service

5.78.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.78.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.78.4. Produces

  • application/json

  • application/xml

5.78.5. Tags

  • generation-data-controller

5.79. Settlement Based Final Generation Plan (SBFGP) Data Listing Service

POST /v1/generation/data/sbfgp

5.79.1. Description

Final Settlement Period Generation Schedule: The generation schedules of power plants that have become unbalanced after the gate closure intraday market.

5.79.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.79.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.79.4. Consumes

  • application/json

  • application/xml

5.79.5. Produces

  • application/json

  • application/xml

5.79.6. Tags

  • generation-data-controller

5.80. Injection/Withdrawal Unit Listing Service

POST /v1/generation/data/uevcb-list

5.80.1. Description

Returns Injection/Withdrawal Unit list by the given organizastion’s id.

5.80.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.80.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.80.4. Consumes

  • application/json

  • application/xml

5.80.5. Produces

  • application/json

  • application/xml

5.80.6. Tags

  • generation-data-controller

5.81. Available Installed Capacity (AIC) Export Service

POST /v1/generation/export/aic

5.81.1. Description

Available Installed Capacity: The active power capacity that a generation unit can provide to the system. ExportsAvailable Installed Capacity (AIC) datas as XLSX, CSV or PDF formats.

5.81.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.81.3. Responses

HTTP Code Description Schema

200

successful operation

5.81.4. Consumes

  • application/json

  • application/xml

5.81.5. Produces

  • application/json

  • application/xml

5.81.6. Tags

  • generation-export-controller

5.82. Final Daily Production Program (FDPP) Export Service

POST /v1/generation/export/dpp

5.82.1. Description

Final day-ahead generation/consumption schedule (FDGS): The generation or consumption values which a settlement feed in-feed out unit anticipates to realize in the following day and notifies the System Operator at the opening of the balancing power market, depending on the obligations of the balancing responsible unit that it is a member of and the result of day-ahead balancing. Exports Final Daily Production Program (FDPP) datas as XLSX, CSV or PDF formats.

5.82.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.82.3. Responses

HTTP Code Description Schema

200

successful operation

5.82.4. Consumes

  • application/json

  • application/xml

5.82.5. Produces

  • application/json

  • application/xml

5.82.6. Tags

  • generation-export-controller

5.83. Final Daily Production Program (FDPP) Export Service

POST /v1/generation/export/dpp-first-version

5.83.1. Description

Final day-ahead generation/consumption schedule (FDGS): The generation or consumption values which a settlement feed in-feed out unit anticipates to realize in the following day and notifies the System Operator at the opening of the balancing power market, depending on the obligations of the balancing responsible unit that it is a member of and the result of day-ahead balancing. Exports Final Daily Production Program (FDPP) datas as XLSX, CSV or PDF formats.

5.83.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.83.3. Responses

HTTP Code Description Schema

200

successful operation

5.83.4. Consumes

  • application/json

  • application/xml

5.83.5. Produces

  • application/json

  • application/xml

5.83.6. Tags

  • generation-export-controller

5.84. Injection Quantity Export Service

POST /v1/generation/export/injection-quantity

5.84.1. Description

Injection Quantity Export Service

5.84.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.84.3. Responses

HTTP Code Description Schema

200

successful operation

5.84.4. Consumes

  • application/json

  • application/xml

5.84.5. Produces

  • application/json

  • application/xml

5.84.6. Tags

  • generation-export-controller

5.85. Licenced Power Plant Investments Export Service

POST /v1/generation/export/licensed-powerplant-investment-list

5.85.1. Description

It is the monthly list of electricity generation facilities that are pre-approved and put into operation by the General Directorate of Energy Affairs. It is the monthly list of electricity generation facilities. Exports Licenced Power Plant Investments datas as XLSX, CSV or PDF formats.

5.85.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.85.3. Responses

HTTP Code Description Schema

200

successful operation

5.85.4. Consumes

  • application/json

  • application/xml

5.85.5. Produces

  • application/json

  • application/xml

5.85.6. Tags

  • generation-export-controller

5.86. Real-Time Generation Export Service

POST /v1/generation/export/realtime-generation

5.86.1. Description

Real-Time Generation Export Service

5.86.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.86.3. Responses

HTTP Code Description Schema

200

successful operation

5.86.4. Consumes

  • application/json

  • application/xml

5.86.5. Produces

  • application/json

  • application/xml

5.86.6. Tags

  • generation-export-controller

5.87. Settlement Based Final Generation Plan (SBFGP) Export Service

POST /v1/generation/export/sbfgp

5.87.1. Description

Final Settlement Period Generation Schedule: The generation schedules of power plants that have become unbalanced after the gate closure intraday market. Exports Settlement Based Final Generation Plan (SBFGP) datas as XLSX, CSV or PDF formats.

5.87.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.87.3. Responses

HTTP Code Description Schema

200

successful operation

5.87.4. Consumes

  • application/json

  • application/xml

5.87.5. Produces

  • application/json

  • application/xml

5.87.6. Tags

  • generation-export-controller

5.88. Main Date Services

GET /v1/main/date-init

5.88.1. Description

Main Date Services

5.88.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.88.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.88.4. Tags

  • main-data-controller

5.89. District List Service

POST /v1/main/district-list

5.89.1. Description

District List Service

5.89.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.89.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.89.4. Consumes

  • application/json

  • application/xml

5.89.5. Produces

  • application/json

  • application/xml

5.89.6. Tags

  • main-data-controller

5.90. Province Listing Service

GET /v1/main/province-list

5.90.1. Description

Listing of Turkiye’s provinces saved in EXIST systems. Istanbul is declared as two items: Istanbul-Asia and Istanbul-Europe.

5.90.2. Parameters

Type Name Description Schema

Header

TGT
required

string

5.90.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.90.4. Produces

  • application/json

  • application/xml

5.90.5. Tags

  • main-data-controller

5.91. Primary Frequency Capacity Amount Data Listing Service

POST /v1/markets/ancillary-services/data/primary-frequency-capacity-amount

5.91.1. Description

It displays hourly total primary frequency capacity volume that the participants need to reserve for the real time frequency balancing.

5.91.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.91.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.91.4. Consumes

  • application/json

  • application/xml

5.91.5. Produces

  • application/json

  • application/xml

5.91.6. Tags

  • markets-ancillary-services-data-controller

5.92. Primary Frequency Capacity Price (PFCP) Data Listing Service

POST /v1/markets/ancillary-services/data/primary-frequency-capacity-price

5.92.1. Description

It displays Primary Frequency Capacity Price determined by the tender on an hourly basis. Tenders are held by Transmission System Operator.

5.92.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.92.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.92.4. Consumes

  • application/json

  • application/xml

5.92.5. Produces

  • application/json

  • application/xml

5.92.6. Tags

  • markets-ancillary-services-data-controller

5.93. Secondary Frequency Capacity Amount Data Listing Service

POST /v1/markets/ancillary-services/data/secondary-frequency-capacity-amount

5.93.1. Description

It displays hourly total secondary frequency capacity volume that the participants need to reserve for the real time frequency balancing.

5.93.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.93.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.93.4. Consumes

  • application/json

  • application/xml

5.93.5. Produces

  • application/json

  • application/xml

5.93.6. Tags

  • markets-ancillary-services-data-controller

5.94. Secondary Frequency Capacity Price (SFCP) Data Listing Service

POST /v1/markets/ancillary-services/data/secondary-frequency-capacity-price

5.94.1. Description

It displays Secondary Frequency Capacity Price determined by the tender on an hourly basis. Tenders are held by Transmission System Operator.

5.94.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.94.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.94.4. Consumes

  • application/json

  • application/xml

5.94.5. Produces

  • application/json

  • application/xml

5.94.6. Tags

  • markets-ancillary-services-data-controller

5.95. Primary Frequency Capacity Amount Export Service

POST /v1/markets/ancillary-services/export/primary-frequency-capacity-amount

5.95.1. Description

It displays hourly total primary frequency capacity volume that the participants need to reserve for the real time frequency balancing. Exports Primary Frequency Capacity Amount datas as XLSX, CSV or PDF formats.

5.95.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.95.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.95.4. Consumes

  • application/json

  • application/xml

5.95.5. Produces

  • application/json

  • application/xml

5.95.6. Tags

  • markets-ancillary-services-export-controller

5.96. Primary Frequency Capacity Price (PFCP) Export Service

POST /v1/markets/ancillary-services/export/primary-frequency-capacity-price

5.96.1. Description

It displays Primary Frequency Capacity Price determined by the tender on an hourly basis. Tenders are held by Transmission System Operator. Exports Primary Frequency Capacity Price (PFCP) datas as XLSX, CSV or PDF formats.

5.96.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.96.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.96.4. Consumes

  • application/json

  • application/xml

5.96.5. Produces

  • application/json

  • application/xml

5.96.6. Tags

  • markets-ancillary-services-export-controller

5.97. Secondary Frequency Capacity Amount Export Service

POST /v1/markets/ancillary-services/export/secondary-frequency-capacity-amount

5.97.1. Description

It displays hourly total secondary frequency capacity volume that the participants need to reserve for the real time frequency balancing. Exports Secondary Frequency Capacity Price (SFCP) datas as XLSX, CSV or PDF formats.

5.97.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.97.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.97.4. Consumes

  • application/json

  • application/xml

5.97.5. Produces

  • application/json

  • application/xml

5.97.6. Tags

  • markets-ancillary-services-export-controller

5.98. Secondary Frequency Capacity Price (SFCP) Export Service

POST /v1/markets/ancillary-services/export/secondary-frequency-capacity-price

5.98.1. Description

It displays Secondary Frequency Capacity Price determined by the tender on an hourly basis. Tenders are held by Transmission System Operator. Exports Secondary Frequency Capacity Price (SFCP) datas as XLSX, CSV or PDF formats.

5.98.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.98.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.98.4. Consumes

  • application/json

  • application/xml

5.98.5. Produces

  • application/json

  • application/xml

5.98.6. Tags

  • markets-ancillary-services-export-controller

5.99. Amount of Bilateral Contracts of EÜAŞ - Authorized Retailers Data Listing Service

POST /v1/markets/bilateral-contracts/data/amount-of-bilateral-contracts

5.99.1. Description

It indicates the monthly totals of bilateral agreements realized between EÜAŞ and Authorized Retail Companies according to the regulated tariff.

5.99.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.99.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.99.4. Consumes

  • application/json

  • application/xml

5.99.5. Produces

  • application/json

  • application/xml

5.99.6. Tags

  • markets-bilateral-contracts-data-controller

5.100. Bilateral Contracts Bid Quantity Data Listing Service

POST /v1/markets/bilateral-contracts/data/bilateral-contracts-bid-quantity

5.100.1. Description

It indicates the purchased power amount through bilateral power contracts.

5.100.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.100.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.100.4. Consumes

  • application/json

  • application/xml

5.100.5. Produces

  • application/json

  • application/xml

5.100.6. Tags

  • markets-bilateral-contracts-data-controller

5.101. Bilateral Contracts Offer Quantity Data Listing Service

POST /v1/markets/bilateral-contracts/data/bilateral-contracts-offer-quantity

5.101.1. Description

It indicates the sold power amount through bilateral power contracts.

5.101.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.101.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.101.4. Consumes

  • application/json

  • application/xml

5.101.5. Produces

  • application/json

  • application/xml

5.101.6. Tags

  • markets-bilateral-contracts-data-controller

5.102. Amount of Bilateral Contracts of EÜAŞ - Authorized Retailers Export Service

POST /v1/markets/bilateral-contracts/export/amount-of-bilateral-contracts

5.102.1. Description

It indicates the monthly totals of bilateral agreements realized between EÜAŞ and Authorized Retail Companies according to the regulated tariff. Exports Amount of Bilateral Contracts of EÜAŞ - Authorized Retailers datas as XLSX, CSV or PDF formats.

5.102.2. Parameters

Type Name Description Schema

Header

TGT
required

string

Body

body
required

Request Body.

5.102.3. Responses

HTTP Code Description Schema

200

Operation successful

400

Bad request. Please check your request

No Content

500

Unexpected error. Please contact EXIST

No Content

5.102.4. Consumes

  • application/json

  • application/xml

5.102.5. Produces

  • application/json

  • application/xml

5.102.6. Tags

  • markets-bilateral-contracts-export-controller

5.103. Bilateral Contracts Bid Quantity Export Service

POST /v1/markets/bilateral-contracts/export/bilateral-contracts-bid-quantity

5.103.1. Description

It indicates the purchased power amount through bilateral power contracts. Exports Bilateral Contracts Bid Quantity datas as XLSX, CSV or PDF formats.

5.103.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.103.3. Responses

HTTP Code Description Schema

200

successful operation

5.103.4. Consumes

  • application/json

  • application/xml

5.103.5. Produces

  • application/json

  • application/xml

5.103.6. Tags

  • markets-bilateral-contracts-export-controller

5.104. Bilateral Contracts Offer Quantity Export Service

POST /v1/markets/bilateral-contracts/export/bilateral-contracts-offer-quantity

5.104.1. Description

It indicates the sold power amount through bilateral power contracts. Exports Bilateral Contracts Offer Quantity datas as XLSX, CSV or PDF formats.

5.104.2. Parameters

Type Name Description Schema

Body

body
required

Request Body.

5.104.3. Responses

HTTP Code Description Schema

200

successful operation

5.104.4. Consumes

  • application/json

  • application/xml

5.104.5. Produces

  • application/json

  • application/xml

5.104.6. Tags

  • markets-bilateral-contracts-export-controller

5.105. Down Regulation Instructions Data Listing Service

POST /v1/markets/bpm/data/order-summary-down

5.105.1. Description

Down Regulation Instructions quantities are released to power units to keep the system balanced in case of energy surplus. Derived from preceding 4 hours' instructions.

5.105.2. Parameters

Type Name Description Schema

Header

TGT
required