Data Service
Introduction
The Data service is used to download data.
User Restrictions
You must have enbm and enbm_download privileges to
access this data.
Calling the Service
The parameters used when calling the service are as follows:
Code |
Required / Optional |
Description |
username |
Required |
The user name |
password |
Required |
The password |
format |
Required |
The type of format required |
action |
Required |
The type of action required |
more ... |
Optional |
Depending on the action selected there will be more
options. |
Specific Details on a per Action Basis
Dependent on the action, the request parameters and response
are different. The table below specifies the actions that are
supported.
Action |
Description |
charts |
Get Available Charts. |
resolutions |
Get Available Resolutions. |
formats |
Get Available Formats. |
data |
Get Data. |
> action=charts
Getting the list of available charts.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=charts
> action=resolutions
Getting the list of available resolutions.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=resolutions
> action=formats
Getting the list of available formats.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=formats
> action=entities
Getting entity information for plants in the market.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=entities
> action=fueltypes
Getting Fuel Type meta information.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=fueltypes
> action=locations
Getting Location meta information.
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=locations
> action=data
NOTE: All these data calls need the entry of a valid username
and password in the given fields.
AVAILABILITY > Availability Heatmap
The Availability Heatmap data can be extracted from the API
to extract percentage availability rates across all the listed
units over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
availhm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=availhm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh
|
AVAILABILITY > Daily Forwards Availability
The Daily Forwards Availability data can be extracted from
the API to extract percentage availability rates projected forwards
2-14 days with this being for a set time range and resolution
(daily). The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
uoudaily |
format |
Required |
The type of format. The value could be xml or csv. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=uoudaily
|
AVAILABILITY > System Margin Summary
The System Margin Summary data can be extracted from the API
to get margin based upon a set of tags that can be extracted from
the browser URL of the System Margin Summary chart during normal
viewing. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
systemmarginoverall |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
series_to_plot |
Optional |
The groupings to break the margin down by, e.g. offerprice.
This defaults to fuel and is as in the browser URL when
picking options in the chart normally.
|
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=systemmarginoverall&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&series_to_plot=offerprice&filter=fuel&fuel=coal
|
AVAILABILITY > Weekly Forwards Availability
The Weekly Forwards Availability data can be extracted from
the API to extract percentage availability rates projected forwards
2-52 weeks with this being for a set time range and resolution
(weeks). The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
uouweekly |
format |
Required |
The type of format. The value could be xml or csv. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=uouweekly
|
BALANCING MECHANISM > Balancing Price Spreads
The Balancing Price Spreads data can be extracted from the API
to get aggregated offer volume totals based upon a set of tags that
can be extracted from the browser URL of the Bid Volumes Summary
chart during normal viewing. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
balspreads |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=balspreads&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh
|
BALANCING MECHANISM > Bid Volumes Summary
The Bid Volumes Summary data can be extracted from the API to
get aggregated bid volume totals based upon a set of tags that can
be extracted from the browser URL of the Bid Volumes Summary chart
during normal viewing. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bidvoloverall |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
series_to_plot |
Optional |
The groupings to break the bid volumes down by, e.g. bidprice.
This defaults to fuel and is as in the browser URL when
picking options in the chart normally.
|
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bidvoloverall&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&series_to_plot=fuel
|
BALANCING MECHANISM > Bid/Offer Prices
The Bid Offer Prices data can be extracted from the API to
get the minimum, average and maximum bid and offer prices by unit
within a grouping over a period of time. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
boprice |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=boprice&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&accdecl=0
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=boprice&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5&accdecl=0
|
BALANCING MECHANISM > Bid/Offer Prices Heatmap
The Bid/Offer Prices Heatmap data can be extracted from the
API to get the prices of Balancing Mechanism accepted prices over
the market. This is not as detailed as other sources, but gives the
same overview given in the front end chart. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
bopricehm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=none&none=null and is as in the
browser URL when picking options in the chart normally.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
bidoffer |
Optional |
Whether to look at Bids (bid) or Offers (offer)
and is as in the browser URL when picking options in the chart
normally. Defaults to bidoffer=offer (Offers)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bopricehm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&filter=none&none=null&accdecl=0&bidoffer=offer
|
BALANCING MECHANISM > Bid/Offer Volumes
The Bid Offer Volumes data can be extracted from the API to
get the Bid and Offer Volumes by unit within a grouping over a
period of time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bovol |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bovol&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&accdecl=0
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bovol&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5&accdecl=0
|
BALANCING MECHANISM > Bid/Offer Volumes Heatmap
The Bid/Offer Volumes Heatmap data can be extracted from the
API to get the volumes of Balancing Mechanism activity as a
percentage of installed capacity over the market. This is not as
detailed as other sources, but gives the same overview given in the
front end chart. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bovolhm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=none&none=null and is as in the
browser URL when picking options in the chart normally.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
bidoffer |
Optional |
Whether to look at Bids (bid) or Offers (offer)
and is as in the browser URL when picking options in the chart
normally. Defaults to bidoffer=offer (Offers)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bovolhm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&filter=none&none=null&accdecl=0&bidoffer=offer
|
BALANCING MECHANISM > BM Unit Bid Profile
The BM Unit Bid Profile data can be extracted from the API to
get the declared bid pair data for a single unit in the market. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bmbidprofile |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=none&none=null and is as in the
browser URL when picking options in the chart normally. This
parameter is only really applicable when trying to get data for
an aggregated filter type.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=data&chart=bmbidprofile&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh&bmunitid=E_BRYP-1
|
BALANCING MECHANISM > BM Unit Offer Profile
The BM Unit Offer Profile data can be extracted from the API
to get the declared offer pair data for a single unit in the
market. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bmofferprofile |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=none&none=null and is as in the
browser URL when picking options in the chart normally. This
parameter is only really applicable when trying to get data for
an aggregated filter type.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=yyy&format=xml&action=data&chart=bmofferprofile&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh&bmunitid=E_BRYP-1
|
BALANCING MECHANISM > Offer Volumes Summary
The Offer Volumes Summary data can be extracted from the API
to get aggregated offer volume totals based upon a set of tags that
can be extracted from the browser URL of the Bid Volumes Summary
chart during normal viewing. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
offervoloverall |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
series_to_plot |
Optional |
The groupings to break the offer volumes down by, e.g. offerprice.
This defaults to fuel and is as in the browser URL when
picking options in the chart normally.
|
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=offervoloverall&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&series_to_plot=fuel
|
DYNAMIC DATA > Dynamic Data Changes
The BM Unit Dynamic Profile data can be extracted from the
API to get the dynamic data declared for a single unit in the
market over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
dynamicdatachanges |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
rampupdown |
Optional |
Indicates whether to show data for ramp up (0) or ramp
down (1). Defaults to rampupdown=0.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=dynamicdatachanges&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&filter=none&none=null&bmunitid=T_ABTH7&rampupdown=1
|
DYNAMIC DATA > Ramp Elbows
The Ramp Elbows data can be extracted from the API to get the
Ramp Rate Elbows by unit within a grouping over a period of time.
The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
rampelbows |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
rampupdown |
Optional |
Indicates whether to show data for ramp up (0) or ramp
down (1). Defaults to rampupdown=0.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=rampelbows&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&rampupdown=0
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=rampelbows&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5&rampupdown=0
|
DYNAMIC DATA > Ramp Rates
The Ramp Rates data can be extracted from the API to get the
Ramp Rates by unit within a grouping over a period of time. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
ramprates |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
rampupdown |
Optional |
Indicates whether to show data for ramp up (0) or ramp
down (1). Defaults to rampupdown=0.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=ramprates&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&rampupdown=0
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=ramprates&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5&rampupdown=0
|
GENERATION > BM Unit Operations
The BM Unit Operations data can be extracted from the API to
get the key unit operations data such as generation and Balancing
Mechanism activity over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bmops |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bmops&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&filter=none&none=null&bmunitid=T_ABTH7
|
GENERATION > Generation & Availability
The Generation & Availability data can be extracted from the
API to get the capacity, availability and generation by unit within
a grouping over a period of time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
gaa |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=gaa&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=gaa&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5
|
GENERATION > Run Hour Heatmap
The Run Hour Heatmap data can be extracted from the API to
extract the run hour frequency rates across all the listed units
over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
runhrshm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=runhrshm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh
|
GENERATION > Run Hours
The Run Hours data can be extracted from the API to get the
number of run hours by unit within a grouping over a period of
time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
runhrs |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=runhrs&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=runhrs&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5
|
GENERATION > Starts
The Starts data can be extracted from the API to get the
number of starts by unit within a grouping over a period of time.
The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
starts |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=starts&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=starts&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5
|
GENERATION > System Generation Summary
The System Generation Summary data can be extracted from the
API to get levels of aggregated generation based upon a set of tags
that can be extracted from the browser URL of the System Generation
Summary chart during normal viewing. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
systemgenoverall |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
series_to_plot |
Optional |
The groupings to break the margin down by, e.g. location.
This defaults to fuel and is as in the browser URL when
picking options in the chart normally.
|
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=systemgenoverall&startdatetime=20190520000000&enddatetime=20190527000000&resolution=hh&series_to_plot=location&filter=fuel&fuel=coal
|
GENERATION > Utilisation Heatmap
The Utilisation Heatmap data can be extracted from the API to
extract the utilisation as a percentage of capacity across all the
listed units over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
utilhm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=utilhm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh
|
IMBALANCES > Imbalances
The Imbalances data can be extracted from the API to get the
size of the imbalance (availability below expected generation) by
unit within a grouping over a period of time. The parameters used
as follows:
Code |
Required/Optional |
Description |
chart |
Required |
imbal |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
filter |
Optional |
The group of units that are of interest e.g. filter=fuel&fuel=coal.
This defaults to filter=fuel&fuel=all and is as in the
browser URL when picking options in the chart normally.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=imbal&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=imbal&startdatetime=20190520000000&enddatetime=20190527000000&filter=fuel&fuel=coal&filter_double=location&location=5
|
IMBALANCES > Imbalances Heatmap
The Imbalances Heatmap data can be extracted from the API to
extract the level of imbalances (availability below expected
generation) as a percentage of capacity across all the listed units
over time. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
imbalhm |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=imbalhm&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh
|
INTERCONNECTORS > By Country Import/Export
The By Country Import/Export data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bycountry |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
outturnsched |
Optional |
Defaults to 0 (outturn data). Other options are 1 (scheduled) and 2 (scheduled da) |
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bycountry&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&outturnsched=0
|
INTERCONNECTORS > Explicit Auction Capacity
The Explicit Auction Capacity data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
atc |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=atc&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh
|
INTERCONNECTORS > Intraday Explicit Requested
The Intraday Explicit Requested data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
intradayexplicit |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
fnborder |
Optional |
Defaults to 0 (Belgium). Other options are 1 (France) and 2 (Netherlands) |
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=intradayexplicit&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&fnborder=0
|
INTERCONNECTORS > Net Transfer Capacity
The Net Transfer Capacity data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
ntc |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
border |
Optional |
Defaults to 0 (Belgium). Other options are 1 (France), 2 (Ireland), 3 (Netherlands),
4 (Norway) and 5 (Denmark) |
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=ntc&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&border=0
|
INTERCONNECTORS > Scheduled vs Outturn
The Scheduled vs Outturn data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
scheduled |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
border |
Optional |
Defaults to 0 (Belgium). Other options are 1 (France), 2 (Ireland), 3 (Netherlands),
4 (Norway) and 5 (Denmark) |
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=scheduled&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&border=0
|
LONGER TERM CHARTS > Annual Fuel Mix
The Annual Fuel Mix data can be extracted from the API to
extract the generation by fuel since 1920. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
annualfuelmix |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=annualfuelmix
|
LONGER TERM CHARTS > Annual Fuel Mix (Simple)
The Annual Fuel Mix (Simple) data can be extracted from the
API to extract the simplified generation by fuel since 1920. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
annualfuelmixsimple |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=annualfuelmixsimple
|
LONGER TERM CHARTS > Monthly Fossil Fuels
The Monthly Fossil Fuels data can be extracted from the API
to extract the monthly fossil fuels progression since 2002. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
monthlyfossilfuels |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=monthlyfossilfuels
|
LONGER TERM CHARTS > Monthly Fuel Mix
The Monthly Fuel Mix data can be extracted from the API to
extract the monthly fuel mix since 2002. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
monthlyfuelmix |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=monthlyfuelmix
|
LONGER TERM CHARTS > Monthly Fuel Mix (Simple)
The Monthly Fuel Mix (Simple) data can be extracted from the
API to extract the simplified monthly fuel mix since 2002. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
monthlyfuelmixsimple |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=monthlyfuelmixsimple
|
LONGER TERM CHARTS > Monthly Renewables Breakdown
The Monthly Renewables Breakdown data can be extracted from
the API to extract the breakdown of renewable generation since
2002. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
renewablebreakdown |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=renewablebreakdown
|
MONTHLY UNIT SUMMARIES > Unit Bid/Offer Prices
The Unit Bid/Offer Prices data can be extracted from the API
to extract on a monthly basis the minimum, average and maximum
prices for bid and offer actions. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsboprice |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsboprice&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
MONTHLY UNIT SUMMARIES > Unit Bid/Offer Volumes
The Unit Bid/Offer Volumes data can be extracted from the API
to extract on a monthly basis the volumes for bid and offer
actions. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsbovol |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
accdecl |
Optional |
Whether to go accepted (0) or declared (1) and is as in
the browser URL when picking options in the chart normally.
Defaults to accdecl=0 (Accepted)
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsbovol&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
MONTHLY UNIT SUMMARIES > Unit Generation & Availability
The Unit Generation & Availability data can be extracted from
the API to extract on a monthly basis the volumes for capacity,
availability and generation. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsgaa |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsgaa&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
MONTHLY UNIT SUMMARIES > Unit Imbalances
The Unit Imbalances data can be extracted from the API to
extract on a monthly basis the imbalance levels. The parameters
used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsimbal |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsimbal&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
MONTHLY UNIT SUMMARIES > Unit Run Hours
The Unit Run Hours data can be extracted from the API to
extract on a monthly basis the run hours for a given unit. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsrunhours |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsrunhours&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
MONTHLY UNIT SUMMARIES > Unit Starts
The Unit Starts data can be extracted from the API to
extract on a monthly basis the starts for a given unit. The
parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
unitsstarts |
filter |
Optional |
The group to show data for, e.g. filter=fuel&fuel=coal.
This defaults to no filter and is as in the browser URL when
picking options in the chart normally.
|
bmunitid |
Optional |
The is the unit id and can be found in the Browser URL.
For instance bmunitid=T_ABTH7.
|
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=unitsstarts&filter=fuel&fuel=all&bmunitid=T_ABTH7&accdecl=0
|
SYSTEM > Boundary Flows
The Boundary Flows data can be extracted from the API to
extract the levels of anticipated flow across a particular
boundary. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
boundaryflows |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
boundaryflows |
Required |
The boundary flow ID as in the Browser URL when viewing
the chart. This is between 1 and 17, e.g. boundaryflows=1.
|
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=boundaryflows&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh&boundaryflows=1
|
SUMMARY SCREENS > Accepted Actions
The Accepted Actions data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
accactions |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=accactions&sd=20200322&sp=15
|
SUMMARY SCREENS > Bid Table
The Bid Table data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bidtable |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bidtable&sd=20200322&sp=15
|
SUMMARY SCREENS > Daily BM Bid Prices
The Daily BM Bid Prices data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
dailybmbidprices |
sd |
Required |
The date in format YYYYMMDD. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=dailybmbidprices&sd=20200322
|
SUMMARY SCREENS > Daily BM Offer Prices
The Daily BM Offer Prices data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
dailybmofferprices |
sd |
Required |
The date in format YYYYMMDD. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=dailybmofferprices&sd=20200322
|
SUMMARY SCREENS > Offer Table
The Offer Table data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
offertable |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=offertable&sd=20200322&sp=15
|
SUMMARY SCREENS > Offer On Table
Code |
Required/Optional |
Description |
chart |
Required |
offerontable |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=offerontable&sd=20200322&sp=15
|
SUMMARY SCREENS > Submitted Bids
The Submitted Bids data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
submittedbids |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=submittedbids&sd=20200322&sp=15
|
SUMMARY SCREENS > Submitted Offers
The Submitted Offers data can be extracted from the API. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
submittedoffers |
sd |
Required |
The date in format YYYYMMDD. |
sp |
Required |
The settlement period. |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=submittedoffers&sd=20200322&sp=15
|
SYSTEM > Boundary Flows
The Boundary Flow Projections data can be extracted from the API. The parameters used are as follows:
Code |
Required/Optional |
Description |
chart |
Required |
boundaryflows |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action, e.g.
hh) |
format |
Required |
The type of format. The value could be xml, csv
or xls. (See 'formats' action)
|
boundaryflows |
Optional |
The bounday to get data for, defaults to North West Scotland B1. Options are
North West Scotland B1 (1), North-South Scotland B2 (2), Sloy Export B3 (3),
SHTEL-SPT B4 (B4), Central-Southern Scotland B5 (5), Scotland-England B6 (6),
Northern England B7 (7), Midlands North B8 (8), Midlands South B9 (9),
South Coast B10 (10), NE & Yorkshire B11 (11), South & SW (B12),
South Wales & SW England B13 (13), London B14 (14), Thames Estuary B15 (15),
NE, Trent & Yorkshire B16 (16) or W Midlands B17 (17).
|
Examples :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=boundaryflows&startdatetime=20190213000000&enddatetime=20190214000000&resolution=hh&boundaryflows=6
|
SYSTEM > BSUoS Price
The BSUoS Price data can be extracted from the API to extract
the outturn BSUoS and the live Balancing Mechanism component of
this value. The parameters used as follows:
Code |
Required/Optional |
Description |
chart |
Required |
bsuosprice |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=bsuosprice&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
SYSTEM > Daily Levy Rate
The Daily Levy Rate data can be extracted from the API to extract
the data. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
dailylevyrate |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
dailylevy |
Optional |
Defaults to 0 Daily Levy Rates. Other options are 1 (Eligible Demand), 2 (Energy Intensive Industries) and 3 (Green Excluded Electricity). |
resolution |
Required |
The type of resolution. (See 'resolutions' action). Must be daily or higher |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=dailylevyrate&dailylevy=1&startdatetime=20180416000000&enddatetime=20180417000000&resolution=da
|
SYSTEM > Frequency
The Frequency data can be extracted from the API to extract
the frequency data and the fuel mix. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
freq |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=freq&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
SYSTEM > Inertia Estimate
The Inertia Estimate data can be extracted from the API. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
inertia |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=inertia&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
SYSTEM > Live Demand
The Live Demand data can be extracted from the API. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
livedemand |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=livedemand&startdatetime=20200521000000&enddatetime=20200521010000&&resolution=mi
|
SYSTEM > Metered Demand (Settlement)
The Metered Demand (Settlement) data can be extracted from the API. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
metereddemand |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
gspgroup |
Required |
The type GSP Group to get data for. Can be National (0), Eastern England (1), East Midlands (2), London (3), Merseyside and North Wales (4), West Midlands (5), North Eastern England (6), North Western England (7), Northern Scotland (8), Southern Scotland (9), South Eastern England (10), Southern England (11), Southern Wales (12), South Western England (13) and Yorkshire (14). |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=metereddemand&gspgroup=0&startdatetime=20200521000000&enddatetime=20200521010000&&resolution=hh
|
SYSTEM > NIV Analysis
The NIV Analysis data can be extracted from the API to extract
the series used to forecast the Net Imbalance Volume. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
nivanalysis |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=nivanalysis&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
SYSTEM > System Fuel Mix
The System Fuel Mix data can be extracted from the API to extract
the fuel mix data. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
systemfuelmix |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=systemfuelmix&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
SYSTEM > System Summary
The System Summary data can be extracted from the API to extract
the markets key system level data series. The parameters used as
follows:
Code |
Required/Optional |
Description |
chart |
Required |
systemsummary |
startdatetime |
Required |
The start date time in format YYYYMMDDHHMMSS. |
enddatetime |
Required |
The end date time in format YYYYMMDDHHMMSS. |
resolution |
Required |
The type of resolution. (See 'resolutions' action) |
format |
Required |
The type of format. The value could be xml or csv
. (See 'formats' action)
|
Example :
https://enbm.netareports.com/dataService?username=xxx&password=xxx&format=xml&action=data&chart=systemsummary&startdatetime=20180416000000&enddatetime=20180417000000&resolution=hh
|
|