get_consumption

Get measured electricity consumption (kWh) per price area and customer group, hourly or summed per day.

Signature: get_consumption(price_area: string, optional, default None; start_date: string, optional, default None; end_date: string, optional, default None; consumption_group: string, optional, default None; resolution: string, optional, default 'day'; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

https://allemannsdata.com/wiki/kilder/elhub/get_consumption/?price_area={price_area}&start_date={start_date}&end_date={end_date}&consumption_group={consumption_group}&resolution=day&limit=25&offset=0

Replace {price_area}, {start_date}, {end_date}, {consumption_group}, {resolution} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/elhub/get_consumption?price_area={price_area}&start_date={start_date}&end_date={end_date}&consumption_group={consumption_group}&resolution=day&limit=25&offset=0.

Parameter	Requirement	JSON type	Description
`price_area`	optional	union	NO1..NO5, or omit for all five areas.
`start_date`	optional	union	First day, YYYY-MM-DD (default: 7 days before end_date).
`end_date`	optional	union	Day after the last day wanted (exclusive), YYYY-MM-DD (default: today). At most one month per call.
`consumption_group`	optional	union	Optional household, cabin, primary (agriculture, fishing), secondary (industry) or tertiary (services). Omit for all.
`resolution`	optional	string	"day" (default) sums each group per local date; "hour" returns the raw hourly rows.
`limit`	optional	integer	Gateway page size; default 25, maximum 100.
`offset`	optional	integer	Number of list items to skip; default 0.

Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/elhub/get_consumption?price_area={price_area}&start_date={start_date}&end_date={end_date}&consumption_group={consumption_group}&resolution=day&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/elhub/get_consumption?price_area={price_area}&start_date={start_date}&end_date={end_date}&consumption_group={consumption_group}&resolution=day&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/elhub/get_consumption?price_area={price_area}&start_date={start_date}&end_date={end_date}&consumption_group={consumption_group}&resolution=day&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "elhub",
  "operation": "get_consumption",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}

Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the get_consumption lookup

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.

AI agent? Read the complete navigation and programming guide.