Octopus Energy Unit Rates — Half-Hourly Prices per Tariff

The actual half-hourly unit rates of an Octopus tariff — price including and excluding VAT, and the exact validity window.

Source: Octopus Energy. Free, no key.

What you get

priceExVat, priceIncVat, validFrom, validTo, paymentMethod, unit, id.

Sample output

{ "priceExVat": 15.2, "priceIncVat": 15.96, "unit": "pence_per_kwh",
  "validFrom": "2026-10-17T22:30:00Z", "validTo": "2026-10-17T23:00:00Z" }

Limitations — read before buying

• ⚠️ The price is in PENCE PER KILOWATT-HOUR, not pounds — and unit is returned so that is never in doubt. Converting to pounds without saying so is the kind of silent 100x error this fleet keeps finding.
• priceExVat and priceIncVat are both returned. Domestic bills use the VAT-inclusive figure.
• The windows are HALF-HOURLY and non-overlapping. validFrom is the id, so a re-run replaces rather than duplicates.
• Yes, the price can be NEGATIVE on an agile tariff — being paid to use electricity is real, not a parsing error.
• This is the RATES endpoint; the tariff catalogue is actor 221. A tariff code is needed to use it.

Pricing

Pay per result.

Fields

Field	Type	What it holds
priceExVat	number	Unit rate excluding VAT, in PENCE PER KILOWATT-HOUR. Octopus quotes in pence, not pounds.
priceIncVat	number	Unit rate including VAT, in PENCE PER KILOWATT-HOUR. The figure a domestic bill is actually built from.
validFrom	string	Date the certificate became valid.
validTo	string	ISO 8601 timestamp up to which this record is valid.
paymentMethod	string	Payment method the rate applies to, where the tariff prices differently by method. Null means it applies to all.
unit	string	The unit the prices are quoted in. Always 'pence_per_kwh' — the tariff quotes unit rates in pence, not pounds, and this field is returned so that is never in doubt.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Octopus Energy Unit Rates — Half-Hourly Prices per Tariff declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Octopus Energy Unit Rates include priceExVat, priceIncVat, validFrom, validTo, paymentMethod and unit.
• Octopus Energy Unit Rates needs no API key, login or account of any kind before its first run.
• Every one of Octopus Energy Unit Rates's 5 inputs is optional, so it runs with no configuration at all.
• Octopus Energy Unit Rates documents priceExVat as: Unit rate excluding VAT, in PENCE PER KILOWATT-HOUR. Octopus quotes in pence, not pounds.
• Every number published about Octopus Energy Unit Rates is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Octopus Energy Unit Rates is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

FAQ

What does Octopus Energy Unit Rates return?

It returns 6 documented output fields — priceExVat, priceIncVat, validFrom, validTo, paymentMethod and unit — each with a declared type and a written description. The full schema is below.

What does Octopus Energy Unit Rates require to run?

Nothing. All 5 inputs are optional and ship with working defaults.

Does Octopus Energy Unit Rates need an API key?

No. It reads only public data and asks for no account.

How is Octopus Energy Unit Rates billed?

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.