Docs Menu
Public API Reference
The free public API serves the generation and renewable project register and 5-minute unit output. No key is needed.
Endpoints

| Request | Returns | Parameters |
|---|---|---|
GET https://renewables.networkmap.energy/api/geojson | Every generation and renewable project as a GeoJSON FeatureCollection | none |
GET https://renewables.networkmap.energy/api/geojson?region=VIC1 | The same, filtered to one market region | region: NSW1, QLD1, SA1, TAS1 or VIC1 |
GET https://renewables.networkmap.energy/api/geojson?listDUIDs | Every unit ID with its site name | none |
GET https://renewables.networkmap.energy/api/generation?duid=ARWF1 | 5-minute output as [timestamp_ms, MW] pairs | duid (required); start, end in epoch milliseconds (default: the last 7 days) |
Project Fields
Each project feature includes, among others: Site Name, Owner, Region, Technology Type, Fuel Type, Nameplate Capacity (MW), Storage Capacity (MWh), Unit Status, DUID (the unit ID), Full Commercial Use Date, Expected Closure Year, DNSP and TNSP with the nearest lines and distances, LGA, Postcode and the AEMO KCI Id. Most values are strings. Missing values are NaN, empty or null. Coordinates is an object with lat and lng.
| Term | Meaning |
|---|---|
| DUID | Dispatchable unit identifier: the market code for a generating or load unit. These pages call it the unit ID. |
| DNSP | Distribution network service provider |
| TNSP | Transmission network service provider |
| LGA | Local government area |
| KCI | Key Connection Information: published connection details for a generating or load unit |
See the Glossary for more terms.
Examples
Example Responses
These are trimmed responses from the public API. ... shows where we removed fields or items. Field names are exact.
Project register: geojson and geojson?region=
Both requests return the same shape. /api/geojson returns every project. /api/geojson?region=TAS1 returns only TAS1 projects. This is one TAS1 feature:
Unit list: geojson?listDUIDs
Each item has a DUID and a Site Name. Projects with no DUID show "NaN".
Unit output: generation?duid=
A 15-minute window for ARWF1. Each pair is [timestamp_ms, MW] for one 5-minute interval of AEMO-published data. Some intervals can be missing from the list, as in this example.
Errors and Empty Results
The API does not always return an error code. Check the HTTP status, and check that the body is valid JSON before you use it.
| Request | What you get |
|---|---|
generation with no duid | HTTP 500 with an empty body |
generation with an unknown duid, for example NOTAUNIT9 | HTTP 500 with an empty body |
generation with a duid in lower case, for example arwf1 | HTTP 500 with an empty body. Use the DUID exactly as listDUIDs shows it. |
start or end that is not a number | HTTP 200 with a text message, for example Invalid start parameter: abc. The body is not JSON. |
start later than end | HTTP 200 with an empty list: [] |
region that is unknown or in lower case, for example XYZ1 or tas1 | HTTP 200 with an empty FeatureCollection: "features":[] |
Limits
The API needs no key. No rate limit is published. The full project list is a large file, so filter by region when you can. For unit output, set start and end to the window you need. If you leave them out, you get the last 7 days. Use the API fairly. For heavy or regular automated use, email support@networkmap.energy.
Data Sources and Terms
The project register blends several public sources, including AEMO generation reports. Unit output is AEMO-published 5-minute data. Use the data for screening, planning and analysis. Check it with the relevant network service provider before detailed design. The Network Map Terms of Use and Disclaimer and Terms & Conditions apply.
See the Integrations guide to load the API into QGIS, Power BI or Excel.