dlt-source-elhub 0.1.0__tar.gz

dlt_source_elhub-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Havbruksdataforeningen
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dlt_source_elhub-0.1.0/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: dlt-source-elhub
+Version: 0.1.0
+Summary: dlt source package for Elhub's Energy Data API: metering points and hourly metering values, via Maskinporten
+Author: Havbruksdataforeningen
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Havbruksdataforeningen/dlt-sources/tree/main/packages/dlt-source-elhub
+Project-URL: Repository, https://github.com/Havbruksdataforeningen/dlt-sources
+Project-URL: Changelog, https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/CHANGELOG.md
+Project-URL: Issues, https://github.com/Havbruksdataforeningen/dlt-sources/issues
+Keywords: dlt,elhub,maskinporten,electricity,energy,etl,elt,data-ingestion
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: dlt>=1.2
+Requires-Dist: PyJWT[crypto]>=2.8
+Dynamic: license-file
+
+# dlt-source-elhub
+
+[![PyPI](https://img.shields.io/pypi/v/dlt-source-elhub.svg)](https://pypi.org/project/dlt-source-elhub/)
+
+A [dlt](https://dlthub.com/) source for [Elhub's Energy Data API](https://api.elhub.no/energy-data-api/metering-points): your organisation's electricity metering points and their hourly metering values, authenticated through Maskinporten, into any dlt destination.
+
+**Records land as the API returns them** — nothing renamed, nothing dropped, no invented child tables. Column names are the API's own, in dlt's usual snake_case. Reshaping belongs in your transform layer, where you can change it without waiting for a release.
+
+The package handles the Maskinporten token, the headers Elhub insists on, envelope unwrapping and a cursor per metering point. It depends on dlt and PyJWT.
+
+## How to start
+
+Before any code: your organisation needs a Maskinporten client with the scope `elhub:enduser`, which Elhub grants to an organisation number on request ([Elhub's guide](https://api.elhub.no/energy-data-api/dataset-guidelines)). The client gives you a client id, a key id and a private key.
+
+```bash
+uv add dlt-source-elhub "dlt[duckdb]"   # any dlt destination works; DuckDB is the one below
+```
+
+Then two files in a `.dlt/` directory beside your script.
+
+`.dlt/config.toml`:
+
+```toml
+[sources.elhub]
+user_agent = "my-company-elhub-pipeline"   # Elhub refuses a request without one
+```
+
+`.dlt/secrets.toml`:
+
+```toml
+[sources.elhub.credentials]
+client_id = "00000000-0000-0000-0000-000000000000"
+kid = "00000000-0000-0000-0000-000000000000"
+private_key = """-----BEGIN PRIVATE KEY-----
+...
+-----END PRIVATE KEY-----"""
+```
+
+Then one script, [`daily_load.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/daily_load.py), on a timer:
+
+```python
+import dlt
+from dlt_source_elhub import elhub_source
+
+pipeline = dlt.pipeline(pipeline_name="elhub", destination="duckdb", dataset_name="elhub_data")
+pipeline.run(elhub_source())
+```
+
+There is no separate backfill step. The first run loads everything Elhub retains for every metering point — three years and 41 days, one request per point — and every run after loads what was inserted since, per point. Schedule it after 03:00 Europe/Oslo: yesterday's hours are inserted around 02:05. Run it soon: Elhub deletes data older than three years and 41 days, so each day a first load waits, a day of history is gone.
+
+Two more examples, a page each: [`backfill.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/backfill.py) re-loads one window without touching the cursors, and [`companies.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/companies.py) reads several companies with one client. From a checkout, run one with `python examples/<name>.py`.
+
+## What it loads
+
+| Resource | Endpoint | Load strategy | Key |
+|---|---|---|---|
+| `metering_points` | `GET /metering-points` | merge | `id` |
+| `metering_values_hour` | `GET /metering-points/{id}` | merge | `meteringPointId`, `startTime`, `direction` |
+
+Both read the dataset `METERING_VALUES_HOUR_RESTRICTED`, the only one the `elhub:enduser` scope answers; the day, month and year datasets are `403` under it, so aggregate downstream.
+
+Three things worth knowing before your first query:
+
+- **`metering_points` is the list of ids, found the only way Elhub offers.** There is no list endpoint; the dataset call without an id returns every point with values in the last 24 hours. A point lands as the API's `id` and `type`, with the values left to the other table. A point gone from the list keeps its row; its `_dlt_load_id` says when it was last seen.
+- **`metering_values_hour` is one row per value**, with the point's `id` as `meteringPointId`. `resolution` is `PT60M` on most points and `PT15M` on some, so never assume 24 rows a day. `direction` is `Out` for consumption and `In` for production, both loaded. A corrected value overwrites the old one, because the key is the interval, not the insert.
+- **The cursor is per metering point**, stored in dlt's resource state under the point's id. That is what makes a new point load its history on first contact, and several companies safe in one pipeline — [how it works](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/REFERENCE.md#the-cursor-is-per-metering-point).
+
+## Configuring a resource
+
+Each resource takes its endpoint's params in snake_case. A date is `YYYY-MM-DD`, read as midnight in Europe/Oslo; an ISO 8601 instant with an offset works too.
+
+```python
+source = elhub_source(consumer_org="999999991")
+source.metering_points.bind(metering_point_ids=["707057500000000001"])
+source.metering_values_hour.bind(start_date="2026-10-01", end_date="2026-10-03")
+pipeline.run(source)
+```
+
+| Param | What to know |
+|---|---|
+| `consumer_org` | On the source. The organisation number of a company that delegated the scope to your client's organisation in Altinn; the token is then issued on its behalf. Leave it out to read the client's own organisation. One source per company. |
+| `initial_insert_date_time` | On the source. Where a point the pipeline has not seen starts: values inserted at or after this instant. Left out, everything Elhub retains. |
+| `metering_point_ids` | On `metering_points`. Keep only these ids; `metering_values_hour` then reads only them. For one new point's history, or a backfill of a few. |
+| `start_date`, `end_date` | On both resources. On `metering_points` they move the discovery window, at most one day wide. On `metering_values_hour` they make the request a backfill: the window is sent as given, and the stored cursor is neither read nor advanced. The end is exclusive on `startTime` in practice. |
+| `insert_date_time` | On `metering_values_hour`. Sent instead of the cursor, which is then neither read nor advanced: values inserted at or after it, over the API's widest window when no dates are bound. |
+| `params` | On every resource, merged into the query string last, so it wins over every named param. The escape hatch for a param the API grows later. |
+| `user_agent`, `headers` | On the source. Elhub answers `403` to a request without a `User-Agent`; `headers` adds any other, such as `X-Elhub-GLN` under another scope. |
+
+Params can also be set in config, per resource:
+
+```toml
+[sources.elhub.metering_values_hour]
+start_date = "2026-10-01"
+end_date = "2026-10-03"
+```
+
+## Compatibility
+
+| `dlt-source-elhub` | Energy Data API |
+|---|---|
+| 0.1.x | v0 |
+
+The API is v0, and Elhub says breaking changes may come. Built against the dated copy of its documentation in [`specs/`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/specs/README.md) and run live against it, last on 2026-10-13, with the scope `elhub:enduser`. The `elhub:thirdparty` scope is not verified.
+
+## Read next
+
+- [**API quirks worth knowing**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/specs/README.md#api-quirks-worth-knowing) — what was measured against the live API: windows, the inclusive `insertDateTime` filter, `204` for empty, when yesterday arrives.
+- [**Reference**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/REFERENCE.md) — the cursor, backfilling, several companies, nesting, what the source does not expose, logging and column types.
+- [**Changelog**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/CHANGELOG.md) and [**contributing**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/LICENSE). The files in `specs/` are Elhub's own API documentation, included as the spec this package is built against. They are Elhub's material, and the licence does not extend to them.

dlt_source_elhub-0.1.0/README.md

@@ -0,0 +1,113 @@
+# dlt-source-elhub
+
+[![PyPI](https://img.shields.io/pypi/v/dlt-source-elhub.svg)](https://pypi.org/project/dlt-source-elhub/)
+
+A [dlt](https://dlthub.com/) source for [Elhub's Energy Data API](https://api.elhub.no/energy-data-api/metering-points): your organisation's electricity metering points and their hourly metering values, authenticated through Maskinporten, into any dlt destination.
+
+**Records land as the API returns them** — nothing renamed, nothing dropped, no invented child tables. Column names are the API's own, in dlt's usual snake_case. Reshaping belongs in your transform layer, where you can change it without waiting for a release.
+
+The package handles the Maskinporten token, the headers Elhub insists on, envelope unwrapping and a cursor per metering point. It depends on dlt and PyJWT.
+
+## How to start
+
+Before any code: your organisation needs a Maskinporten client with the scope `elhub:enduser`, which Elhub grants to an organisation number on request ([Elhub's guide](https://api.elhub.no/energy-data-api/dataset-guidelines)). The client gives you a client id, a key id and a private key.
+
+```bash
+uv add dlt-source-elhub "dlt[duckdb]"   # any dlt destination works; DuckDB is the one below
+```
+
+Then two files in a `.dlt/` directory beside your script.
+
+`.dlt/config.toml`:
+
+```toml
+[sources.elhub]
+user_agent = "my-company-elhub-pipeline"   # Elhub refuses a request without one
+```
+
+`.dlt/secrets.toml`:
+
+```toml
+[sources.elhub.credentials]
+client_id = "00000000-0000-0000-0000-000000000000"
+kid = "00000000-0000-0000-0000-000000000000"
+private_key = """-----BEGIN PRIVATE KEY-----
+...
+-----END PRIVATE KEY-----"""
+```
+
+Then one script, [`daily_load.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/daily_load.py), on a timer:
+
+```python
+import dlt
+from dlt_source_elhub import elhub_source
+
+pipeline = dlt.pipeline(pipeline_name="elhub", destination="duckdb", dataset_name="elhub_data")
+pipeline.run(elhub_source())
+```
+
+There is no separate backfill step. The first run loads everything Elhub retains for every metering point — three years and 41 days, one request per point — and every run after loads what was inserted since, per point. Schedule it after 03:00 Europe/Oslo: yesterday's hours are inserted around 02:05. Run it soon: Elhub deletes data older than three years and 41 days, so each day a first load waits, a day of history is gone.
+
+Two more examples, a page each: [`backfill.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/backfill.py) re-loads one window without touching the cursors, and [`companies.py`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/examples/companies.py) reads several companies with one client. From a checkout, run one with `python examples/<name>.py`.
+
+## What it loads
+
+| Resource | Endpoint | Load strategy | Key |
+|---|---|---|---|
+| `metering_points` | `GET /metering-points` | merge | `id` |
+| `metering_values_hour` | `GET /metering-points/{id}` | merge | `meteringPointId`, `startTime`, `direction` |
+
+Both read the dataset `METERING_VALUES_HOUR_RESTRICTED`, the only one the `elhub:enduser` scope answers; the day, month and year datasets are `403` under it, so aggregate downstream.
+
+Three things worth knowing before your first query:
+
+- **`metering_points` is the list of ids, found the only way Elhub offers.** There is no list endpoint; the dataset call without an id returns every point with values in the last 24 hours. A point lands as the API's `id` and `type`, with the values left to the other table. A point gone from the list keeps its row; its `_dlt_load_id` says when it was last seen.
+- **`metering_values_hour` is one row per value**, with the point's `id` as `meteringPointId`. `resolution` is `PT60M` on most points and `PT15M` on some, so never assume 24 rows a day. `direction` is `Out` for consumption and `In` for production, both loaded. A corrected value overwrites the old one, because the key is the interval, not the insert.
+- **The cursor is per metering point**, stored in dlt's resource state under the point's id. That is what makes a new point load its history on first contact, and several companies safe in one pipeline — [how it works](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/REFERENCE.md#the-cursor-is-per-metering-point).
+
+## Configuring a resource
+
+Each resource takes its endpoint's params in snake_case. A date is `YYYY-MM-DD`, read as midnight in Europe/Oslo; an ISO 8601 instant with an offset works too.
+
+```python
+source = elhub_source(consumer_org="999999991")
+source.metering_points.bind(metering_point_ids=["707057500000000001"])
+source.metering_values_hour.bind(start_date="2026-10-01", end_date="2026-10-03")
+pipeline.run(source)
+```
+
+| Param | What to know |
+|---|---|
+| `consumer_org` | On the source. The organisation number of a company that delegated the scope to your client's organisation in Altinn; the token is then issued on its behalf. Leave it out to read the client's own organisation. One source per company. |
+| `initial_insert_date_time` | On the source. Where a point the pipeline has not seen starts: values inserted at or after this instant. Left out, everything Elhub retains. |
+| `metering_point_ids` | On `metering_points`. Keep only these ids; `metering_values_hour` then reads only them. For one new point's history, or a backfill of a few. |
+| `start_date`, `end_date` | On both resources. On `metering_points` they move the discovery window, at most one day wide. On `metering_values_hour` they make the request a backfill: the window is sent as given, and the stored cursor is neither read nor advanced. The end is exclusive on `startTime` in practice. |
+| `insert_date_time` | On `metering_values_hour`. Sent instead of the cursor, which is then neither read nor advanced: values inserted at or after it, over the API's widest window when no dates are bound. |
+| `params` | On every resource, merged into the query string last, so it wins over every named param. The escape hatch for a param the API grows later. |
+| `user_agent`, `headers` | On the source. Elhub answers `403` to a request without a `User-Agent`; `headers` adds any other, such as `X-Elhub-GLN` under another scope. |
+
+Params can also be set in config, per resource:
+
+```toml
+[sources.elhub.metering_values_hour]
+start_date = "2026-10-01"
+end_date = "2026-10-03"
+```
+
+## Compatibility
+
+| `dlt-source-elhub` | Energy Data API |
+|---|---|
+| 0.1.x | v0 |
+
+The API is v0, and Elhub says breaking changes may come. Built against the dated copy of its documentation in [`specs/`](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/specs/README.md) and run live against it, last on 2026-10-13, with the scope `elhub:enduser`. The `elhub:thirdparty` scope is not verified.
+
+## Read next
+
+- [**API quirks worth knowing**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/specs/README.md#api-quirks-worth-knowing) — what was measured against the live API: windows, the inclusive `insertDateTime` filter, `204` for empty, when yesterday arrives.
+- [**Reference**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/REFERENCE.md) — the cursor, backfilling, several companies, nesting, what the source does not expose, logging and column types.
+- [**Changelog**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/CHANGELOG.md) and [**contributing**](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/LICENSE). The files in `specs/` are Elhub's own API documentation, included as the spec this package is built against. They are Elhub's material, and the licence does not extend to them.

dlt_source_elhub-0.1.0/pyproject.toml

@@ -0,0 +1,103 @@
+[project]
+name = "dlt-source-elhub"
+version = "0.1.0"
+description = "dlt source package for Elhub's Energy Data API: metering points and hourly metering values, via Maskinporten"
+readme = "README.md"
+requires-python = ">=3.11"
+# PEP 639: an SPDX expression plus the file, not a classifier. The two forms
+# cannot be combined, so there is deliberately no "License ::" classifier below.
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Havbruksdataforeningen" }]
+keywords = ["dlt", "elhub", "maskinporten", "electricity", "energy", "etl", "elt", "data-ingestion"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Database",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Typing :: Typed",
+]
+dependencies = [
+    # >=1.2 for the RESTClient and configspec helpers used here.
+    "dlt>=1.2",
+    # The Maskinporten grant is a JWT signed with the client's RSA key. PyJWT is what dlt's own
+    # OAuthJWTAuth signs with; [crypto] brings the cryptography package that does the RS256.
+    "PyJWT[crypto]>=2.8",
+]
+
+[project.urls]
+Homepage = "https://github.com/Havbruksdataforeningen/dlt-sources/tree/main/packages/dlt-source-elhub"
+Repository = "https://github.com/Havbruksdataforeningen/dlt-sources"
+Changelog = "https://github.com/Havbruksdataforeningen/dlt-sources/blob/main/packages/dlt-source-elhub/CHANGELOG.md"
+Issues = "https://github.com/Havbruksdataforeningen/dlt-sources/issues"
+
+[dependency-groups]
+dev = [
+    "dlt[duckdb]>=1.2",
+    "pytest>=8.0",
+    "pytest-cov>=6.0",
+    "pyright>=1.1",
+    "ruff>=0.8",
+]
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+# Ships the PEP 561 marker, so a consumer's type checker reads this package's
+# annotations instead of treating it as untyped.
+[tool.setuptools.package-data]
+dlt_source_elhub = ["py.typed"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py311"
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+# S is ruff's port of bandit: hardcoded credentials, requests without a
+# timeout, disabled TLS verification — the risks of code that talks to a
+# supplier's API with credentials. Don't add bandit itself without a check it
+# catches that S does not.
+select = ["E", "W", "F", "I", "B", "C4", "UP", "SIM", "RUF", "S"]
+ignore = ["E501", "B008"]
+
+[tool.ruff.lint.per-file-ignores]
+# Tests use assert (S101) — that is what a test is. They also query their own
+# local duckdb with f-string SQL (S608): table names cannot be bound as
+# parameters, and the interpolated values are test constants.
+"tests/**" = ["S101", "S608"]
+
+[tool.ruff.lint.isort]
+known-first-party = ["dlt_source_elhub"]
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+
+[tool.pyright]
+pythonVersion = "3.11"
+typeCheckingMode = "basic"
+include = ["src", "tests", "examples"]
+exclude = [".venv", ".dlt", ".agent"]
+venvPath = "."
+venv = ".venv"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+# The default run is offline — it needs no Elhub credentials, so it means
+# the same thing in CI and on a laptop. Run the live tests with -m integration.
+addopts = "-m 'not integration'"
+markers = [
+    "integration: marks tests that hit the real Elhub API (run with -m integration)",
+]
+filterwarnings = [
+    "ignore::DeprecationWarning:dlt.extract.validation",
+]
+
+[build-system]
+requires = ["setuptools>=77.0.3"]  # >=77 for PEP 639 license / license-files
+build-backend = "setuptools.build_meta"

dlt_source_elhub-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

dlt_source_elhub-0.1.0/src/dlt_source_elhub/__init__.py

@@ -0,0 +1,9 @@
+"""dlt source package for Elhub's Energy Data API."""
+
+from importlib.metadata import version
+
+from dlt_source_elhub.elhub import ALL_RETAINED_HISTORY, elhub_source
+from dlt_source_elhub.maskinporten import MaskinportenAuth, MaskinportenCredentials
+
+__version__ = version("dlt-source-elhub")
+__all__ = ["ALL_RETAINED_HISTORY", "MaskinportenAuth", "MaskinportenCredentials", "elhub_source"]

dlt_source_elhub-0.1.0/src/dlt_source_elhub/columns.py

@@ -0,0 +1,22 @@
+"""Column hints: the API's own field names, typed per `specs/meta-metering-points.json`."""
+
+from dlt.common.schema.typing import TTableSchemaColumns
+
+METERING_POINT_COLUMNS: TTableSchemaColumns = {
+    "id": {"data_type": "text", "nullable": False},
+    "type": {"data_type": "text"},
+}
+
+# `meteringPointId` is the id of the point the value is nested under, named as Elhub's other datasets name it.
+METERING_VALUES_HOUR_COLUMNS: TTableSchemaColumns = {
+    "meteringPointId": {"data_type": "text", "nullable": False},
+    "startTime": {"data_type": "text", "nullable": False},
+    "endTime": {"data_type": "text", "nullable": False},
+    "direction": {"data_type": "text", "nullable": False},
+    "quantityKwh": {"data_type": "double"},
+    "resolution": {"data_type": "text"},
+    "measurementName": {"data_type": "text"},
+    "productCode": {"data_type": "bigint"},
+    "endUserId": {"data_type": "text"},
+    "insertDateTime": {"data_type": "text"},
+}