APX DataCapture API 7 Version 2.11

Transcription

1 APX DataCapture API 7 Version 2.11

2 1 Document Control Document Location An electronic version of this document is available in the Member s area of APX Group s website ( A valid username and password are required. Revision History Revision Date Version Author Revision Summary 23 January Various Update of MSI s for UK Power and GSM markets 13 July Various Removal of the Zeebrugge Market and inclusion of the ZTP Market 19 March Angela Allen Update for TTF MFE changes 21 June Angela Allen Update for NBP & CUR Markets 4 July Roseline Chan Converted document in APX brand 30 April Gordon White Changes due to migration of ICE Endex s Markets to WebICE. 9 September Auke van der Zijden Update of new OTC segment; OTC 1 BLOCK 3 February Marc Bills Update with Half Hour Power Auction market 29 April Auke van der Zijden, Update with new reports for Auction trades. 14 September Roy Hetharia Update with Unique Trade Identifier 21 March J. Merkus Changed SSL to TLS 1.0 (section 3.2) Approvals This document requires the following approvals. Name Signature Title Date of Issue Matthijs Nijpels Operations Director 2

3 Contents page Document Control 1 Document Location 2 Revision History 2 Approvals 2 1 Introduction Environments 6 2 The DataCapture process 7 3 Requesting Data General Protocol File Formats Data Format Error codes 10 4 Request & Response Specifications Continuous Order Capture Own Continuous Trade Data on contract time Own Continuous Trade Data on delivery period All Continuous Trades Data Own Auction Trade Data on contract time SAP SMP Chargelines Auction indices General matching report Manifest Errors and Reversed Trades System requirements 37 5 Usage Guidelines Making sure you get all trades when using Private Trade Capture 39

4 6 Appendix I: Platform Identifiers, Market Segment Identifiers and Instrument Codes Platform Identifiers Default Market Set APX Power UK APX UK Power auction APX UK Power Half Hour auction APX Gas UK 47 7 Appendix II: XML output format OrderCapture 49 8 Appendix III: XML2 output format OrderCapture TradeCapture PublicTradeCapture Auction indices General matching Error 69 9 Appendix IV: Error codes and messages Introduction The DataCapture system is an environment that provides Members the ability to quickly and easily capture a range of information. The data available for capture is: Orders in the market; Members own trades by contract time; Members own trades by delivery period; All trades; Own Auction Trade Data on contract time; SAP/SMP Archive (APX Gas UK market only); Chargelines;

5 Auction indices; General matching. This document describes the functionality of the DataCapture system that APX offers its Members, explaining how the system can be used and what information can be retrieved. Chapter 3 describes the process and explains the flow of information and the overall architecture. Chapter 4 contains specific information about the requests for Order & TradeCapture. Chapter 5 contains information about the requests and the responses. Appendix I contains a description of the Platform Identifiers, Market Segment Identifiers and the Instrument codes. Appendix II and III describe the XML and XML2 response specifications. Appendix IV contains a list of error codes and the related messages Environments The DataCapture system is available for our UK Power, UK Gas and Continental Gas markets. All platforms will be integrated in one system, which can be reached through the following URLs: Production: Standby: Test: The following section describes the differences between the price and volume units of each exchange. APX Gas TTF Price: Euros per megawatt hour ( /MWh) Volume unit: Megawatt (MW)

6 APX Gas ZTP Price: Euros per megawatt hour ( /MWh) Volume unit: Megawatt (MW) APX Gas UK Price: Pence per Therm ( /Therm) Volume unit: Therms/day APX Power UK Price: GBPs per megawatt hour ( /MWh) Volume unit: Megawatt (MW) 6 2 The DataCapture process Order and Trade information can be captured from the APX web server. Access is available either via the Internet or a leased line connection to APX. This environment is connected to a database that is linked to a central database used by the trading application, thus delivering close to real-time information. To retrieve the data a request has to be made to a component situated at an APX web server. This request can be made by a custom-made Member application or by using a standard web browser. The Data Capture process:

7 7 3 Requesting Data 3.1 General The system distinguishes the following request types. Members can request: Orders in the market; Members own trades by contract time Members own trades by delivery period; All trades; Own Auction Trade Data on contract time; The SAP/SMP summary report. (UK Gas market only); Chargelines; Auction indices;

8 General matching. The following types of requests can be gathered from the base URL with the report parameter. All requests, except for the SAP/SMP summary report will be available by accessing the old URL (for backwards compatibility). The URL for continuous orders is: The URL for private continuous trades by contract time is: The URL for private continuous trades by delivery period is: The URL for all continuous trades is: The URL for private auction trades by contract time is: The URL for SAP SMP report is: The URL for the chargelines report is: The URL for the auction indices is: 8 The URL for the general matching report is:

9 9 3.2 Protocol APX will assign username and initial password combinations to the Members. Passwords can be changed by logging on to the BackOffice website, (using the DataCapture username and password). Communication with the DataCapture web server is only possible using a Transport Layer Security (TLS 1.0) connection. Username and password authentication will happen by parsing these as parameters within the URL. It is possible to use a custom made application or a standard web browser to request the system for trades. 3.3 File Formats The DataCapture web server currently supports three output formats: 'csv' and two XML formats: 'xml' and xml2. While default output format is 'csv' we strongly recommend using the xml2 output format since the other formats are only maintained for backwards compatibility. CSV The csv format is known by common spreadsheet software (including Microsoft Excel). This commaseparated data will be sent as plain text. In a web browser this will result in the comma separated data being displayed in the browser window. If you want to load this data in your spreadsheet program, save the output data to a text-file and open it in your spreadsheet program. XML & XML2 DataCapture can also return data in two different XML-formats. Specifications of these XML-formats can be found in Appendix II and Appendix III. These formats are especially suited for applications querying the system. 3.4 Data Format The format of numbers returned, are one of three formats: Integer; Numeric, or Decimal. Integers are whole numbers only. Numeric has a floating number of decimal places; the number following the comma in the format indicates the maximum number of decimals. E.g. Numeric (10,3) has a maximum of three decimal places. Decimals have a fixed number of decimal places; the number following the comma in the format indicates the number of decimals. 3.5 Error codes Due to the nature of Internet communication, data can sometimes be interrupted, causing incomplete information to be received. To be able to identify any problems in the transmission each output format employs its own validation method.

10 10 In addition to communication errors between the Member and the DataCapture server, other errors can occur. In this situation an error-code and message will be returned. An explanation of the error codes can be found in Appendix IV. CSV To verify the completeness of received data the CSV-file returns a special footer line. The last line of the returned data does not contain order or trade data but contains information about the request. If a request was successful, the last line will contain a # followed by the number of returned lines (for example if a request returns 24 data-rows, this will be #24), followed by a comma and then followed by a value consisting of the date and time that the database was last updated. By including the last database update time in the footer, users will know what time to use as the next begintime to ensure that no data is missed. Example: For some reason the Trade Capture application has been closed for queries. You requested an XML response. The system will return: <?xml version="1.0" encoding="iso "?> <response status="-41" timestamp="" msg="the system is closed"> </response> In this case try again in a little while or inform APX who may be able to explain the reason for this closure. XML2 The completeness of an XML document can be easily verified by checking whether it is well-formed. Any request that did not experience connection problems returns a well-formed XML document. At least a <response> element will be returned, containing <header> element with a status, timestamp and msg element. On a successful request the status will be 1. In case of an error the status will contain the errorcode. The timestamp will be the date/time the database was last updated. In case of an error the msg attribute will contain the error-message. 11

11 Example: The report you ve requested doesn t exist. You requested an XML2 response. The system will return: <?xml version="1.0" encoding="iso "?> <Response xsi:nonamespaceschemalocation=" xmlns:xsi=" <Header> <Status>-101</Status> <Message>Report error: Unknown report: chargeline </Message> <Timestamp> T11:11:48Z</Timestamp> </Header> </Response> In this case try again in a little while or inform APX who may be able to explain the reason for this closure. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: 12

12 4 Request & Response Specifications 4.1 Continuous Order Capture Parameters for orders request <market ID string>&output=<format>&platform=<platform> The table shows the parameters that should be submitted to the DataCapture URL when requesting continuous orders: Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Market Platform output User Name as provided by APX Text Yes Password as provided by APX Text Yes Allows orders only in specified market segments to be returned Allows orders only in specified platforms to be returned Specifies the output format to be used. Default format is csv Semi-colon separated text string x;y;z;a;b;c Semi-colon separated text string x;y;z;a;b;c Text, either csv, xml or xml2 No, omitting or invalid means default market set will be returned No, omitting or invalid means all platforms will be returned No, omitting or invalid for csv format The platform identifiers, market segment identifiers and the default market set can be found in Appendix Examples:

13 To retrieve all, submit the following: To retrieve all orders in the OCM_TITLE MarketSegment for OCM Title in CSV format, submit the following: LE Replace username and password in the URLs above with those provided. 14 Returned data The data returned is a snapshot of all the open continuous orders in the market at the time of the request. The information is anonymous so that Members are not able to identify orders from other

14 Members. The following table describes the fields present in the output file. In the case of a CSV response, the fields will be returned in this order. In the XML response, the values will be put in the appropriate fields (see Appendix II and Appendix III for the XML specifications). Field Format Description Instrument Code Text Identifying the contract type & block Market segment Identifier Text The identifier representing the market segment Buy / Sell Flag Text = B or S denoting Buy or Sell Price Decimal (10,2) or null The order price in the appropriate format Volume Numeric (10,3) The Volume in the appropriate format Order ID Integer ID of the order submitted to the market Version Number Integer Version of the order submitted to the market Begintime in GMT Endtime in GMT Date time, YYYY-MM-DD hh:mm:ss Date time, YYYY-MM-DD hh:mm:ss Begintime of the first delivery period of the order or null for forward trades Endtime of the last delivery period of the order or null for forward trades Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: Example file (CSV): OCM TITLE WED 06-DEC-06, OCM_TITLE,B,12.00,100,10345,2, :00:00, ,05:00:00 OCM TITLE WED 06-DEC-06, OCM_TITLE,S,13.04,50,10346,0, :00:00, ,05:00:00 #2, Order IDs and Version Numbers orders submitted into the Market have a unique Order ID and a version number. If an order is modified, or partially matched then the version number is changed, but the original order ID remains the same. E.g. an order for 100MW is submitted in to the market, and is allocated an order ID = 1234 and version=0. If the order is partially matched for 25MW, then the remaining pending order ID is still 1234 but the version changes to 1, and the volume is now 75MW. Be advised: this report will not return any auction order data Own Continuous Trade Data on contract time

15 Parameters for own trades request egin=<begin time>&end=<endtime>&market=<market segment ID string>&account=<integer string>&output =<format>&platform=<platform> The table shows the parameters that should be included in the request made to the web server to retrieve your own continuous trades that have been traded within a specific date/time range and for some or all continuous market segments, and some or all of your position accounts. Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Begin User Name as provided by APX Password as provided by APX Trades transacted within this period will be retrieved. (GMT) Text Text Date time, YYYYMMDDhhmmss Yes Yes Yes End Market Allows trades only in specified market segments to be returned Platform Account output Allows orders only in specified platforms to be returned It is possible to specify specific position account(s). Only trades on this account will be retrieved. Specifies the output-format to be used. Default format is csv Date time, YYYYMMDDhhmmss Semicolon separated string x;y;z;a;b;c Semicolon separated string x;y;z;a;b;c Semicolon separated Integer string n;n;n;n;n;n Text, either csv, xml or xml2 No, omitting this parameter means until now No, omitting or invalid means default market set will be returned No, omitting or invalid means all platforms will be returned No, omitting or invalid parameter means all accounts No, omitting or invalid for csv format 16 Note that the begin/end parameters relate to the time the trade was created in the system, NOT the time the trade delivers. The market segment identifiers and the default market set can be found in Appendix I. Position account identifiers will be provided to individual Members on request.

16 Examples: To retrieve own trades matched at a time greater than 23:10:10 on 9 th June 2006 GMT until present time in XML2 format, submit the following: &output=xml2 To retrieve own trades for just one position account, with account ID 2, in OCM Title only, traded at a time greater than 16:10:10 on 17 th December 2006 GMT until a time equal to or less than 18:19:07 on 17 th December 2006 GMT, submit the following: &end= &market=OCM_TITLE&account=2 Replace username and password in the URLs above with those provided. Returned Data The following table describes the fields present in the output file generated by the own trades request. In the case of a CSV response, the fields will be returned in this order. In the XML response, the values will be put in the appropriate fields (see Appendix II and Appendix III for the XML specifications). Field Format Description Uniquely identifying the trade and equivalent to ID Contract ID Integer in Contract book in Trading Application Instrument Code Text Identifying the trade type & block Order number Integer Refers to the order number used in the Trading Application Own Position Account Integer Contains the ID of the position account used by the requesting Member For bilateral markets will contain the ID of the Position account of Integer position account used by the counterparty, all other markets, field will be null the counterparty Market Segment Identifier Text The identifier representing the market segment Buy / Sell Flag Text = B or S denoting Buy or Sell Begintime in GMT Date time, YYYY-MM-DD hh:mm:ss Begintime of the first delivery period in a trade, or null for forward trades 17 Endtime in GMT Date time, YYYY-MM-DD hh:mm:ss Endtime of the last delivery period in a trade or null for forward trades

17 A positive number for the trading volume Volume Numeric (10,3) expressed in the appropriate format Price Decimal (10,2) or null The actual trade price in the appropriate format Time of trade GMT LoginID Reversed Contract ID Unique Trade Identifier Date time, YYYY-MM-DD hh:mm:ss Text Integer Integer The actual date and time the trade was done The name of the user that submitted the bid or offer. For bilateral trades, this field will be null If this record is for a Trade that reverses an erroneous trade then this field will contain the Contract ID of the Trade reversed, otherwise it will be null (see section 4.10) Unique Trade Identifier used in REMIT Reporting. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: Requesting your own trades will bring back all continuous trades made by you as the Member, including the login that transacted the trade. The login field for bilateral trades will only be populated where the Member initiated the bilateral order and not when the Member confirmed the order. For Members who will be regularly polling the system to retrieve their trades on an ongoing basis, it is recommended that the users submit a 'begin' Date/Time equal to the Date/Time returned by the system as the used endtime, and leave the 'end' Date/Time blank. This will ensure that no trades are missed and will keep the load on the system to a minimum. Example for request for own trades on contract time (CSV): 12756,OCM TITLE WED 06-DEC-06,1010,7,,OCM_TITLE,S, :00:00, :00:00,200,15.50, :45:23,Trader2, 12757,OCM TITLE WED 06-DEC-06,1011,7,,OCM_TITLE,S, :00:00, :00:00,200,15.50, :46:23,Trader2, #2, The last data record is a reversing trade for an earlier trade (12756) (see section 5.7 for further details of reversing trades) Own Continuous Trade Data on delivery period

18 Parameters for own trades request begin=<begin time>&end=<endtime>&market=<market segment ID string>&account=<integer string>&output =<format>&platform=<platform> The table shows the parameters that should be included in the request made to the web server to retrieve your own continuous trades that have the delivery period within a specific date/time range and for some or all market segments, and some or all of your position accounts Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Begin End Market Platform Account output User Name as provided by APX Text Yes Password as provided by APX Text Yes Trades with a delivery period within this period will be retrieved. (GMT) Allows orders only in specified market segments to be returned Allows orders only in specified platforms to be returned It is possible to specify specific position account(s). Only trades on this account will be retrieved. Specifies the output-format to be used. Default format is csv Date time, YYYYMMDDhhmmss Date time, YYYYMMDDhhmmss Semicolon separated string x;y;z;a;b;c Semicolon separated string x;y;z;a;b;c Semicolon separated Integer string n;n;n;n;n;n Specifies the outputformat to be used. Default format is csv Yes No, omitting this parameter means until now No, omitting or invalid means default market set will be returned No, omitting or invalid means all platforms will be returned No, omitting or invalid parameter means all accounts Specifies the outputformat to be used. Default format is csv 19 Note that the begin/end parameters relate to the time the trade delivers, NOT the time the trade was created in the system. The market segment identifiers and the default market set can be found in Appendix I. Position account identifiers will be provided to individual Members on request.

19 Examples: To retrieve own trades matched with a delivery time greater than 23:10:10 on 9 th June 2006 GMT until present time, submit the following: To retrieve own trades for just one position account, with account ID 2, in the Weekend Market of TTF only, with a delivery period within 23:10:10 on 9 th June 2006 and 03:19:07 on 10 th June 2006 in CSV format, submit the following: &end= &market=TTF_WKD&account=2&output=csv Replace username and password in the URLs above with those provided. Returned Data The following table describes the fields present in the output file generated by the own trades request. In the case of a CSV response, the fields will be returned in this order. In the XML response, the values will be put in the appropriate fields (see Appendix II and Appendix III for the XML specifications). Field Format Description Contract ID Integer Uniquely identifying the trade and equivalent to ID in Contract book in Trading Application Instrument Code Text Identifying the trade type & block Order number Own Position Account Position account of the counterparty Integer Integer Integer Refers to the order number used in the Trading Application Contains the ID of the position account used by the requesting Member For bilateral markets will contain the ID of the position account used by the counterparty, all other markets, field will be null 20 Market Segment Identifier Text The identifier representing the market segment Buy / Sell Flag Text = B or S denoting Buy or Sell Begintime in GMT Date time, YYYY-MM-DD hh:mm:ss Begintime of the first delivery period in a trade, or null for forward trades

20 Endtime in GMT Date time, YYYY-MM-DD hh:mm:ss Volume Numeric (10,3) Endtime of the last delivery period in a trade or null for forward trades A positive number for the trading volume expressed in the appropriate format Price Decimal (10,2) or null The actual trade price in the appropriate format Time of trade GMT LoginID Reversed Contract ID Unique Trade Identifier Date time, YYYY-MM-DD hh:mm:ss Text Integer Integer The actual date and time the trade was done The name of the user that submitted the bid or offer. For bilateral trades, this field will be null If this record is for a Trade that reverses an erroneous trade then this field will contain the Contract ID of the Trade reversed, otherwise it will be null (see section 4.10) Unique Trade Identifier used in REMIT Reporting. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: Requesting your own continuous trades will bring back all trades made by you as the Member, including the login that transacted the trade. The login field for bilateral trades will only be populated where the Member initiated the bilateral order and not when the Member confirmed the order. For Members who will be regularly polling the system to retrieve their trades on an ongoing basis, it is recommended that the users submit a 'begin' Date/Time equal to the Date/Time returned by the system as the used endtime, and leave the 'end' Date/Time blank. This will ensure that no trades are missed and will keep the load on the system to a minimum. 21

21 Example for request for own trades on delivery period (CSV): 12756,TTF 15 JUL TO EOD,1010,7,,TTF_06,S, :00:00, :00:00,200,15.50, :45:23,Trader2, 12757,TTF 15 JUL TO EOD,1011,7,,TTF_06,S, :00:00, :00:00,200,15.50, :46:23,Trader2, 12767,TTF 15 JUL TO EOD,1010,7,,TTF_06,B, :00:00, :00:00,200,15.50, :15:17,Operator,12756 #3, The last data record is a reversing trade for an earlier trade (12756) (see section 5.7 for further details of reversing trades) 4.4 All Continuous Trades Data Parameters for all trades request begintime>&end=<endtime>&market=<market segment ID String>&output=<format>&platform=<platform> The table shows the parameters that should be included in the request made to the web server to retrieve all continuous trades traded within a specific date/time range and for some or all market segments: Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Begin End Market User Name as provided by APX Password as provided by APX Trades transacted at a time greater than this time will be retrieved (GMT) Trades transacted at a time equal to or before this time within this period will be retrieved (GMT) Allows orders only in specified market segments to be returned Text Text Date/time YYYYMMDDhhmmss Date/time YYYYMMDDhhmmss Semicolon separated string x;y;z;a;b;c Yes Yes Yes No, omitting this parameter means until now No, omitting or invalid means default market set will be returned 22

22 Platform Allows orders only in specified platforms to be returned Semicolon separated string x;y;z;a;b;c No, omitting or invalid means all platforms will be returned output Specifies the output format to be used. Default format is csv Text, either csv, xml or xml2 No, omitting or invalid for csv format Note that the begin/end parameters relate to the time the order was created, NOT the time the trade delivers. The market segment identifiers and the default market set can be found in Appendix I. Examples: To retrieve all trades traded at a time greater than 23:10:10 on 9 th June 2006 GMT until present time, submit the following: To retrieve all trades matched at a time greater than 23:10:10 on 9 th June 2006 GMT until a time equal to or less than 03:19:07 on 10 th June 2006 GMT in XML format, submit the following: &end= &output=xml Replace username and password in the URLs above with those provided. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: For Members who will be regularly polling the system to retrieve all trades on an ongoing basis, it is recommended that the users submit a 'begin' Date/Time equal to the Date/Time returned by the system as the used end time, and leave the 'end' Date/Time blank. This will ensure that no trades are missed and will keep the load on the system to a minimum. Returned data The following table describes the columns present in the output file generated by the public trades request. In the case of a CSV response, the fields will be returned in this order. In the XML response, the values will be put in the appropriate fields (see Appendix II and Appendix III for the XML specifications). 23

23 Field Format Description Contract ID Integer Uniquely identifying the trade Instrument Code Text Identifying the trade type & block Market Segment Identifier Text Identifying the market segment type Buy / Sell Text Contains a B for buying or a S for selling. Begintime in GMT Date time, YYYY-MM-DD hh:mm:ss Date time, YYYY-MM-DD hh:mm:ss Begintime of the first delivery period in a trade or null for forward trades Endtime of the last delivery period in a trade or null for forward trades Endtime in GMT A positive number for the trading volume Volume Numeric (10,3) expressed in the appropriate format Price Decimal (10,2) The actual trade price in the appropriate format Time of trade GMT Reversed Contract ID Unique Trade Identifier Date time, YYYY-MM-DD hh:mm:ss Integer Integer The actual date and time the trade was done. If this record is for a Trade that reverses an erroneous trade then this field will contain the Contract ID of the Trade reversed, otherwise it will be null. (see section 4.10) Unique Trade Identifier used in REMIT Reporting. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: Own Auction Trade Data on contract time Parameters for own auction trades request ord>&begin=<begin time>&end=<endtime>&market=<market segment ID string>&account=<integer string>&output=<format>&platform=<platform> The table shows the parameters that should be included in the request made to the web server to retrieve your own Auction trades that have been traded within a specific date/time range and for some or all auction market segments, and some or all of your position accounts. 24

24 Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Begin User Name as provided by APX Password as provided by APX Trades transacted within this period will be retrieved. (GMT) Text Text Date time, YYYYMMDDhhmmss Yes Yes Yes End Market Allows trades only in specified market segments to be returned Platform Account output Allows orders only in specified platforms to be returned It is possible to specify specific position account(s). Only trades on this account will be retrieved. Specifies the output-format to be used. Default format is csv Date time, YYYYMMDDhhmmss Semicolon separated string x;y;z;a;b;c Semicolon separated string x;y;z;a;b;c Semicolon separated Integer string n;n;n;n;n;n Text, either csv, xml or xml2 No, omitting or invalid means all platforms will be returned Yes, the specific auction market needs to be selected No, omitting or invalid means all platforms will be returned No, omitting or invalid parameter means all accounts No, omitting or invalid for csv format Note that the begin/end parameters relate to the time the trade was created in the system (matched), NOT the time the trade delivers. The market segment identifiers and the default market set can be found in Appendix I. Position account identifiers will be provided to individual Members on request. For the Auction trade data there is a predefined time window to capture the data. In addition to this there is also maximum time period of requesting the data is predefined. These limits can be found in chapter 5 (Usage Guidelines). 25

25 Examples : To retrieve own auction trades matched at a time greater than 11:50:10 on 9th March 2015 GMT until present time in XML2 format, submit the following: egin= &output=xml2 To retrieve own auction trades for just one position account, with account ID 2, in UK Power Auction, traded at a time greater than 12:55:00 on 17th March 2015 GMT until a time equal to or less than 13:05:00 on 17th March 2015 GMT, submit the following: privateauctiontrades &user=username&pass=password&begin= &end= &market=A_1HR&account=2 Replace username and password in the URLs above with those provided Returned Data The following table describes the fields present in the output file generated by the own trades request. In the case of a CSV response, the fields will be returned in this order. In the XML response, the values will be put in the appropriate fields (see Appendix II and Appendix III for the XML specifications). Field Format Description Uniquely identifying the trade and equivalent to ID Contract ID Integer in Contract book in Trading Application Instrument Code Text Identifying the trade type & block Order number Integer Refers to the order number used in the Trading Application Own Position Account Integer Contains the ID of the position account used by the requesting Member For bilateral markets will contain the ID of the Position account of Integer position account used by the counterparty, all other markets, field will be null the counterparty Market Segment Identifier Text The identifier representing the market segment Buy / Sell Flag Text = B or S denoting Buy or Sell Begintime in GMT Date time, YYYY-MM-DD hh:mm:ss Begintime of the first delivery period in a trade, or null for forward trades 26

26 Date time, YYYY-MM-DD hh:mm:ss Endtime of the last delivery period in a trade or null for forward trades Endtime in GMT A positive number for the trading volume Volume Numeric (10,3) expressed in the appropriate format Price Decimal (10,2) or null The actual trade price in the appropriate format Time of trade GMT LoginID Reversed Contract ID Unique Trade Identifier Date time, YYYY-MM-DD hh:mm:ss Text Integer Integer The actual date and time the trade was done The name of the user that submitted the bid or offer. For bilateral trades, this field will be null If this record is for a Trade that reverses an erroneous trade then this field will contain the Contract ID of the Trade reversed, otherwise it will be null (see section 4.10) Unique Trade Identifier used in REMIT Reporting. Note that the timestamps in the XML2 specifications comply with the XML Date/time standard as described here: Requesting your own trades will bring back all auction trades made by you as the Member, including the login that transacted the trade. The login field for bilateral trades will only be populated where the Member initiated the bilateral order and not when the Member confirmed the order. For Members who will be regularly polling the system to retrieve their trades on an ongoing basis, it is recommended that the users submit a 'begin' Date/Time equal to the Date/Time returned by the system as the used end time, and leave the 'end' Date/Time blank. This will ensure that no trades are missed and will keep the load on the system to a minimum. Example for request for own auction trades on contract time (CSV): ,1H , ,368,,A_1HR,B, :00:00, :00:00,20,15, :08:33,APXUK_TEST, ,1H , ,368,,A_1HR,B, :00:00, :00:00,20,15, :08:33,APXUK_TEST, ,1H , ,368,,A_1HR,B, :00:00, :00:00,20,15, :08:33,APXUK_TEST, ,1H , ,368,,A_1HR,B, :00:00, :00:00,20,15, :08:33,APXUK_TEST, #24,

27 4.6 SAP SMP Parameters for SAP SMP request <format> The table shows the parameters that should be submitted to the DataCapture URL when requesting the SAP SMP summary: Parameter name Description Definition Mandatory Report The report to display Text Yes User Pass Begin User Name as provided by APX Password as provided by APX specifies the output format to be used. Default format is csv Text Text Text, either csv or xml2 Yes Yes Yes Examples: To retrieve the market summary: Replace username and password in the URLs above with those provided. Returned data The data returned is market summary for SMP SAP. The following table describes the fields present in the output file. In the XML2 response, the values will be put in the appropriate fields (see Appendix III for the XML2 specifications). Field Format Description Applying Date Date, YYYY-MM-DD Applying date SMPBuyPrice Decimal (10,4) or null The order price for SMP buy SMPBuyTime Date time, YYYY-MM-DD hh:mm:ss Last update timestamp 28 SMPBuyStatus Text Default, Current or Final

28 SMPSellPrice Decimal (10,4) or null The order price for SMP Sell SMPSellTime Date time, YYYY-MM-DD hh:mm:ss Last update timestamp SMPSellStatus Text Default, Current or Final SAPPrice Decimal (10,4) or null The order price for SAP SAPTime Date time, YYYY-MM-DD hh:mm:ss Last update timestamp SAPStatus Text Default, Current or Final Note that the timestamps in the XML2 specifications comply with the XML and Date standard as described here: Example file (CSV): ,13.03, :34:21,default,25.32, :10:52,default,10.75, :44:10,default #3, Chargelines Parameters for chargelines request =<D_or_M>&begin=<date/month>&end=<date/month>&chargecodes=<charge_code_ID_string>&st atus=<f or P>&output=<format>&platform=<platform> The table shows the parameters that should be submitted to the DataCapture URL when requesting the chargelines request: Parameter name Description Definition Mandatory 29 User Pass Username as provided by APX Power UK Text Yes Password as provided by APX Power UK Text Yes

29 Type Type of the statement to request to retrieve data for = D for daily or = W for weekly = M for monthly Yes Begin End charge codes Chargelines for statements with this date/month or later will be returned. Chargelines for statements with this date/month or earlier will be returned It is possible to specify specific charge code(s) 1. Only chargelines with these charge code(s) will be retrieved Daily / Weekly = YYYYMMDD Monthly =YYYYMM Daily / Weekly = YYYYMMDD Monthly =YYYYMM Semicolon separated Integer string n;n;n;n;n;n Yes No, omitting this parameter means end is the same as begin No, omitting this parameter means all charge codes Status To filter whether only chargelines on final or preliminary statements are returned = F or = P No, omitting means all chargelines will be returned Platform output Allows orders only in specified platforms to be returned Specifies the output format to be used. Default format is csv Semicolon separated string x;y;z;a;b;c Text, either csv, xml or xml2 No, omitting or invalid means all platforms will be returned No, omitting or invalid for csv format 30 Examples: To retrieve all chargelines for the final daily statements from March 1st 2004 till March 31st 2004, submit the following: egin= &end= &status=f

30 Replace username and password in the URL above with those provided To retrieve all chargelines for the monthly statements of March 2004 with the charge codes or 10021, submit the following: egin=200403&chargecodes=10021 Returned data The data returned is a snapshot of the chargelines in the system at the time of the request. The following table describes the fields present in the output file: Field Format Description Chargeline ID Integer (10) Uniquely identifying chargeline identifier Statement Number Integer (10) ID number of the statement the chargeline belongs to Settlement Period Type Weekly: Date YYYY-MM- DD W Position Account ID Integer (10) Settlement period of the statement Type of the statement this chargeline belongs to. Weekly Identifier of the position account for this chargeline, or null Position Account Name String Name of the position account for this chargeline, or null Contract ID Integer (10) Identifier of the contract this chargeline belongs to, or null Instrument Code String Instrument code, or null 31 Charge code Integer (10) Charge code for this chargeline Description String Description for this chargeline Amount Numeric (10,4) Total amount of the charge of this chargeline Price Numeric (14,3) Price per volume or null Total Volume Numeric (14,3) Volume in MWh or null

31 Volume per unit Numeric (10,3) MW or null Charge or Credit 'Charge' or 'Credit' Whether this is a charge or a credit Fee Numeric (5,4) The applicable fee or null VAT Numeric (5,4) VAT rate or null Final Invoice Number String VAT invoice number, or null Example file: 10256,25, ,D,8,Production Account,256,HH ,10080,Spot Market Matching Fee,2.625,,50,100,Charge,0.0525,, ,25, ,D,8,Production Account,256,HH ,10025,VAT on Fees (from Member),0.459,,50,100,Charge,,0.175, ,25, ,D,8,Production Account,256,HH ,10022,Energy Purchases,925,18.5,50,100,Charge,,, ,25, ,D,8,Production Account,256,HH ,10024,VAT on Energy Purchases, ,,50,100,Charge,,0.175, ,25, ,D,8,Production Account,262,4H ,10080,Spot Market Matching Fee,10.5,,200,50,Charge,0.0525,, ,25, ,D,8,Production Account,262,4H ,10025,VAT on Fees (from Member),1.838,,200,50,Charge,,0.175, ,25, ,D,8,Production Account,262,4H ,10021,Energy Sales,4070,20.35,200,50,Credit,,, ,25, ,D,8,Production Account,262,4H ,10023,VAT on Energy Sales,712.25,,200,50,Credit,,0.175,587 #8, The statement ID and the final invoice number are not the same. Each chargeline will have a statement ID which indicates which chargelines will appear on the same statement. Chargelines on preliminary statements will not have a final invoice number. When a preliminary statement goes 32 final, the final invoice number will be allocated. The final invoice number will be the same as appears on the VAT invoice on the back-office website. When submitting a request with the status parameter set to F, only those Chargelines with a final invoice number will be returned. If the status is set to P, then only those chargelines without a final invoice number will be returned. If the status parameter is omitted, then all will be returned. 4.8 Auction indices

32 Parameters for auction indices request utput=<format> The table shows the parameters that should be submitted to the DataCapture URL when requesting the auction indices: Parameter name Description Definition Mandatory Report The report to display Text Yes User User Name as provided by APX Text Yes Pass Password as provided by APX Text Yes Market Allows orders only in specified market segments to be returned Semicolon separated string x;y;z;a;b;c No, omitting or invalid means default market set will be returned output specifies the output format to be used. Default format is csv Text, either csv or xml2 Yes Examples: To retrieve the auction indices: Replace username and password in the URLs above with those provided. 33 Returned data The data returned is the Baseload, Peakload and Off Peakload indices for the applicable market segment. Please be aware that these values are produced only once each day, and once produced the values will not change. The following table describes the fields present in the output file. In the XML2 response, the values will be put in the appropriate fields (see Appendix III for the XML2 specifications). Field Format Description

33 Applying Date Date, YYYY-MM-DD Applying date Type Text Index type / Index period Price Decimal (10,4) or null The matching price for the specific period Volume Decimal (11,3) or null Total matching volume for the specific period Time Date time, YYYY-MM-DD hh:mm:ss Date and time of the auction Note that the timestamps in the XML2 specifications comply with the XML and Date standard as described here: Example file (CSV): ,31.875,16594, :45:23, ,8490, :45:23, ,8104, :45:23 #1, General matching report Parameters for general matching request &output=<format>

34 The table shows the parameters that should be submitted to the DataCapture URL when requesting the UK Power auction general matching results: Parameter name Description Definition Mandatory Report The report to display Text Yes User User Name as provided by APX Password as provided by Pass APX Market Allows orders only in specified market segments to be returned output Specifies the output format to be used. Default format is csv Text Text Semicolon separated string x;y;z;a;b;c Text, either csv or xml2 Yes Yes No, omitting or invalid means default market set will be returned No, omitting or invalid means default output will be returned Examples: To retrieve the general matching results: Replace username and password in the URLs above with those provided. Returned data The data returned is the general matching results for the applicable market segment. The following table describes the fields present in the output file. In the XML2 response, the values will be put in the appropriate fields (see Appendix III for the XML2 specifications). Field Format Description 35 Market Segment Identifier Text The identifier representing the market segment Time Date time, YYYY-MM-DD hh:mm:ss Time of the auction DeliveryStart Date time, YYYY-MM-DD hh:mm:ss Time the delivery period starts Instrument Text Identifying the trade type & block

35 MCP Decimal (10,2) or null Market Clearing Price MCV Numeric (10,3) Market Clearing Volume Note that the timestamps in the XML2 specifications comply with the XML and Date standard as described here: 36 Example file (CSV): A_1HR_T, :43:02, :00:00,1H ,0,0 A_1HR_T, :43:02, :00:00,1H ,0,0 A_1HR_T, :43:02, :00:00,1H ,0,0 A_1HR_T, :43:02, :00:00,1H ,0,0 A_1HR_T, :43:02, :00:00,1H ,0,0 A_1HR, :44:26, :00:00,1H ,30,625 A_1HR, :44:26, :00:00,1H ,32,545 A_1HR, :44:26, :00:00,1H ,32,545 A_1HR, :44:26, :00:00,1H ,32,545 A_1HR, :44:26, :00:00,1H ,27,625

36 A_1HR, :44:26, :00:00,1H ,27,625 A_1HR, :44:26, :00:00,1H ,27,627 A_1HR, :44:26, :00:00,1H ,27,967 A_1HR, :44:26, :00:00,1H ,32,575 A_1HR, :44:26, :00:00,1H ,34,575 A_1HR, :44:26, :00:00,1H ,34,575 A_1HR, :44:26, :00:00,1H ,34,575 A_1HR, :44:26, :00:00,1H ,32,725 A_1HR, :44:26, :00:00,1H ,33,725 A_1HR, :44:26, :00:00,1H ,34,725 A_1HR, :44:26, :00:00,1H ,29,1015 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,34,750 A_1HR, :44:26, :00:00,1H ,33,750 A_1HR, :44:26, :00:00,1H ,32,750 #29, Manifest Errors and Reversed Trades If a Trade has been made in error, then it is cancelled out by entering a reverse trade, i.e. a trade with the same price & volume, but with the Buyer and Seller reversed. The reversing trade will be linked to the original trade by the inclusion of the original trade s contract ID as an additional field in the reversing trade s record. In the All Trades file, a manifest error of this kind will normally result in two reversed trades, as for each cleared trade; there exists two trades in the system: Buyer to APX and APX to Seller System requirements Using an application 37 Members can connect their own systems to the APX DataCapture system making use of the standard https protocol. All modern programming languages include libraries to submit web requests and process the response. Please refer to the documentation of your programming language of choice. Using a web browser It is possible to use a standard web browser to submit a request to the DataCapture system. The web browser will receive the comma-separated data and display it in the browser-window. This can then be saved or copied to a spreadsheet program.