# GB Electricity Imbalance Price Monitor

Export GB electricity imbalance prices in GBP/MWh by settlement period. Track published price revisions, negative prices and source timestamps from Elexon without an API key.

Canonical product page: https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/

## Example input

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

## Ready-to-use input recipes

These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running.

[Default input](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/evidence.json)

### Read three recent GB imbalance prices

Read the latest three published periods from the preceding UTC date, with GBP/MWh units and publication timestamps.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-1.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

### Inspect the first three settlement periods

Read periods 1–3 from the preceding UTC date. London settlement periods retain their exact UTC start timestamps.

```json
{
  "startPeriod": 1,
  "endPeriod": 3,
  "maxResults": 3,
  "comparePrevious": false
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-2.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

### Compare a fixed day for price revisions

Keep a dated window for repeat checks of observed Elexon price corrections. First run establishes the baseline.

```json
{
  "settlementDate": "2026-11-20",
  "startPeriod": 1,
  "endPeriod": 3,
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "dated-price-revisions"
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/recipe-3.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 3 saved rows. This does not establish current availability.

[All example inputs](https://mayd-it.com/data-tools/actors/gb-electricity-imbalance-monitor/examples/index.json)
## Choose this tool

Energy analysts, battery and flexibility researchers, power-cost reporting teams and automation builders working with published GB settlement data.

Useful output columns: `title`, `settlementDate`, `settlementPeriod`, `startTime`, `systemBuyPrice`, `systemSellPrice`, `priceUnit`, `isNegativePrice`, `netImbalanceVolume`.

## Practical workflow

Start with three recent periods from the preceding UTC date. Keep GBP/MWh, London settlement date and UTC start time together when joining records. Pin a settlement date and snapshot name to compare subsequent source corrections.

## Check the fit

Indicative imbalance prices can be revised; they are not household tariffs or executable market quotes. No future-price forecast, battery dispatch instruction or savings guarantee. The date response may omit periods that have not been published. Source-day coverage is explicit. Use 46/48/50 settlement periods according to London daylight-saving transitions.

## Real output sample

One selected row from a 2026-11-21 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: c6XaR0DJ5zrNVutMC. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "elexon:2026-11-20:48",
  "title": "GB 2026-11-20 — settlement period 48",
  "settlementDate": "2026-11-20",
  "settlementPeriod": 48,
  "startTime": "2026-11-20T23:30:00.000Z",
  "systemBuyPrice": 218,
  "systemSellPrice": 218,
  "priceUnit": "GBP/MWh",
  "isNegativePrice": false,
  "netImbalanceVolume": 44.62708333333333,
  "sourcePublishedAt": "2026-11-21T00:18:28.000Z",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/system-prices/2026-11-20?format=json",
  "url": "https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/system-prices/2026-11-20?format=json"
}
```




## Full guide

![GB Electricity Imbalance Price Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/gb-electricity-imbalance-monitor-8fc7e4429630.png)

# GB Electricity Imbalance Price Monitor

<!-- MAYDIT-BANNER -->

Export GB electricity imbalance prices in GBP/MWh by settlement period. Track published price revisions, negative prices and source timestamps from Elexon without an API key.

**Built for:** Energy analysts, battery and flexibility researchers, power-cost reporting teams and automation builders working with published GB settlement data.

## Start with three real observations

Run the default input to collect a small, traceable source window. No source API key, login, proxy or paid source subscription is required. The Actor exports actual public source records and reports source failures without creating paid diagnostic rows.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

Open the dataset for JSON/CSV, **SUMMARY** for coverage and **RUN_REPORT** for a readable result. A successful bounded run does not prove the full source universe was collected.

## Three practical recipes

### Read three recent GB imbalance prices

Read the latest three published periods from the preceding UTC date, with GBP/MWh units and publication timestamps.

```json
{
  "maxResults": 3,
  "comparePrevious": false
}
```

### Inspect the first three settlement periods

Read periods 1–3 from the preceding UTC date. London settlement periods retain their exact UTC start timestamps.

```json
{
  "startPeriod": 1,
  "endPeriod": 3,
  "maxResults": 3,
  "comparePrevious": false
}
```

### Compare a fixed day for price revisions

Keep a dated window for repeat checks of observed Elexon price corrections. First run establishes the baseline.

```json
{
  "settlementDate": "2026-11-20",
  "startPeriod": 1,
  "endPeriod": 3,
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "dated-price-revisions"
}
```

## Understand the result

Each row is a published GB settlement-period observation. `systemBuyPrice` and `systemSellPrice` are **GBP per MWh**. `netImbalanceVolume` uses **MWh**, not MW; absent optional source values remain null. Negative prices remain negative. `settlementDate` and `settlementPeriod` use London market time; `startTime` and `endTime` use UTC. The code handles 46, 48 and 50 half-hour periods without silently adding or dropping the clock-change periods.

`sourcePublishedAt` is Elexon’s publication timestamp and `observedAt` is our separate retrieval time. `priceStatus` stays `indicative_subject_to_revision`: these values are not final settlement guarantees, retail electricity bills, forward forecasts or executable offers. The source publication timestamp alone does not trigger a price-change event. `pricesChanged`, `systemBuyPriceChange` and `systemSellPriceChange` compare the actual saved values when previous observations exist.

Blank `settlementDate` means the previous **UTC calendar date**, a stable default that avoids much of the current-day publication lag. To monitor corrections, pin an explicit date. `startPeriod`/`endPeriod` bound the requested period range and `maxResults` selects the latest periods in that range. The source is fetched once for the date. `SUMMARY.sourceCoverage` includes missing source periods, expected day length, matched count and selected-window count; an otherwise successful selected window can coexist with an incomplete source day.

| Output | Purpose |
| --- | --- |
| `recordId`, `sourceUrl` | Stable source identity and a link to the official data. |
| `observedAt` | Retrieval time, separate from source issuance/publication. |
| `comparisonStatus`, `changedFields`, `previous` | New, changed or unchanged source fields on requested comparisons. |
| `SUMMARY` | Selected coverage, source errors, limits and history status. |

## Changes you can trust

Run the same selection and `snapshotName` sequentially with `comparePrevious:true`. The first complete run establishes a baseline in the named `gb-electricity-imbalance-monitor-history` store. `onlyChanges:true` also enables comparison and can correctly emit zero rows on unchanged repeats. Observation time and age alone never create changed records.

History advances only after confirmed output from a complete selected window. Source errors, interrupted output, exhausted charge allowance, deadlines and concurrent history writers prevent baseline replacement. Prior records are preserved; absent source records never imply removals, cancellations or a resolved operational condition. This Actor does not schedule itself or send alerts automatically; use your own saved task, schedule or integration.

## Use with other Mayd It Actors

- [EIA Power Project Monitor](https://apify.com/maydit/eia-power-project-monitor): Put operating price observations beside US generation-project research while keeping the markets separate.
- [GPU Cloud Rate Monitor](https://apify.com/maydit/gpu-cloud-rate-monitor): Compare compute pricing with an energy research feed without treating imbalance prices as a cloud provider’s actual electricity bill.

Keep source identities and timestamps when joining datasets. Correlation is a research observation, not proof of causation.

## Pricing and bounds

Standard event pricing: **$0.002 per confirmed saved observation**, plus **$0.00005 Actor Start**. Three rows total **$0.00605** in Actor event charges. Plan discounts and any applicable Apify platform charges are separate. A comparison with zero changed rows can still incur start/platform usage. Reports and errors are never paid dataset rows. Set a maximum total charge in Run options.

The default is three rows with a 60-second whole-run budget (30–120 seconds allowed). Each official request has a 20-second timeout and a 2 MiB response cap, within the remaining deadline. A 502/503/504 can receive one bounded retry after 500 ms; access denials, rate limits, malformed data and exhausted budgets are not bypassed. The actual platform timeout is also respected. Maximum output is 50 settlement periods from one date.

## Source limits and provenance

- Indicative imbalance prices can be revised; they are not household tariffs or executable market quotes.
- No future-price forecast, battery dispatch instruction or savings guarantee.
- The date response may omit periods that have not been published. Source-day coverage is explicit.
- Use 46/48/50 settlement periods according to London daylight-saving transitions.

[Official source documentation](https://developer.data.elexon.co.uk/) · [Source data and interpretation](https://www.elexon.co.uk/bsc/settlement/imbalance-pricing/) · [Source field definitions](https://www.elexon.co.uk/bsc/glossary/settlement-period/) · [Data licence](https://www.elexon.co.uk/bsc/data/balancing-mechanism-reporting-agent/copyright-licence-bmrs-data/)

Contains Elexon BMRS data; attribution and reuse remain subject to the linked BMRS Data Licence. Independent of and not endorsed by Elexon or NESO. This is a research/data tool, not financial advice or an automated dispatch system.

Report reproducible issues in the Actor’s Issues tab with a non-sensitive input and run link.

## Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [EIA Power Project Monitor](https://apify.com/maydit/eia-power-project-monitor)

Add separate power-infrastructure context to an electricity-market research workflow.

1. Analyze GB settlement periods and published imbalance-price revisions.
2. Run the EIA project monitor separately for US power-project research.
3. Keep geographic scope and publication dates separate in a cross-market dashboard.

GB settlement prices and US project records cannot be directly joined into a tariff or price forecast.

### [GPU Cloud Rate Monitor – Runpod & Lambda Price Changes](https://apify.com/maydit/gpu-cloud-rate-monitor)

Compare electricity-market observations with separately published GPU cloud offers.

1. Retain GBP/MWh settlement prices and their settlement date.
2. Collect supported GPU provider offers in a separate run.
3. Display the two series with explicit units and source timestamps for infrastructure research.

Cloud rental prices do not track GB imbalance prices directly. This does not calculate workload costs or execute trades.
