# MaStR Scraper: German Solar, Battery & Wind Register (`dach_data_tools/mastr-energy-register-scraper`) Actor

Scrape Germany's official energy register (Marktstammdatenregister): every solar park, battery storage and wind turbine with capacity, location and commissioning date — plus a lead list of operator companies with email, phone, website and register number.

- **URL**: https://apify.com/dach_data_tools/mastr-energy-register-scraper.md
- **Developed by:** [nqvrl](https://apify.com/dach_data_tools) (community)
- **Categories:** Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## MaStR Scraper: German Solar, Battery & Wind Register

Scrape the **Marktstammdatenregister (MaStR)** — the official federal register of every energy installation in Germany, run by the Bundesnetzagentur — and get a **lead list of the companies operating them**, in the same run.

- **~9.7 million installations:** solar parks, rooftop PV, battery storage, wind turbines, biomass, hydro and more — the single most complete dataset of the German energy transition
- **Operator lead list included:** the register publishes every operating company's address, email, phone, website, legal form and commercial register number
- **Fast:** official public data endpoint — no browser, no CAPTCHAs, hundreds of installations per minute
- **Cheap:** $1 per 1,000 installations, $8 per 1,000 operator profiles

### Two datasets per run

**Installations** — one item per unit: capacity (kW), commissioning & shutdown dates, address with coordinates, voltage level, technology details (module count & orientation for solar, manufacturer/model/hub height for wind, storage capacity for batteries), operator name + MaStR ID.

**Operators** — one row per company:

```json
{
    "name": "Photovoltaikkraftwerk Tramm GmbH & Co. KG",
    "street": "Poststraße 15",
    "postalCode": "20354",
    "city": "Hamburg",
    "email": "info@example.de",
    "phone": "040...",
    "website": "www.example.de",
    "registerCourt": "Amtsgericht Hamburg",
    "registerNumber": "HRA126655",
    "vatId": "DE267151615",
    "isSme": true,
    "totalCapacityKwInRun": 171604.68,
    "installationsInRun": 2
}
```

### Use cases

- **Solar installers & O\&M**: installations above X kW in your region, with the operating company behind each one
- **Battery retrofit & repowering sales**: plants commissioned before 2010 or 2015 — aging systems ready for upgrades
- **Energy market research**: new capacity by state/district/month, technology mix, operator consolidation
- **B2B lead-gen**: every company owning grid-scale assets, with direct contact details
- **Grid / network analysts**: capacity, voltage level and grid operator per location

### Input

| Field | Description |
|---|---|
| `energyType` | Solar/PV, battery storage, wind, biomass, hydro, natural gas — or all |
| `minCapacityKw` / `maxCapacityKw` | Capacity range (100+ kW skips home rooftops → commercial/utility scale) |
| `state` | Any Bundesland or all of Germany |
| `postalCodePrefix`, `city` | Location filters |
| `commissionedAfter` / `commissionedBefore` | Commissioning date range — new systems or old plants |
| `status` | In operation / planned / any |
| `onlyOrganizations` | Skip private rooftops, keep company-owned only (default on — private owners are anonymised anyway) |
| `operatorNameContains` | e.g. `"Stadtwerke"` or `"Solarpark"` |
| `sortBy` | Largest first / newest first |
| `maxItems` | How many installations |
| `includeOperatorContacts` | Emit the operator lead list |

### Examples

**Solar parks > 1 MW in Bavaria:**

```json
{ "energyType": "2495", "minCapacityKw": 1000, "state": "1403" }
```

**All battery storage commissioned in the last 90 days:**

```json
{ "energyType": "2496", "commissionedAfter": "2026-08-10", "sortBy": "InbetriebnahmeDatum-desc" }
```

**Old PV plants (>100 kW) due for repowering in NRW:**

```json
{ "energyType": "2495", "minCapacityKw": 100, "state": "1409", "commissionedBefore": "2011-01-01" }
```

### Data & license

Public data from the Marktstammdatenregister, licensed under **Datenlizenz Deutschland – Namensnennung – Version 2.0** (open data, attribution required). Private persons' names are anonymised by the register itself — only organisation contact data is returned. Please credit the source and process business contact data responsibly (GDPR still applies downstream).

# Actor input Schema

## `energyType` (type: `string`):

Which kind of installation to scrape.

## `minCapacityKw` (type: `integer`):

Only installations with gross capacity above this value. 100+ kW filters out home rooftops and keeps commercial / utility-scale systems.

## `maxCapacityKw` (type: `integer`):

Only installations with gross capacity below this value. Leave empty for no limit.

## `state` (type: `string`):

Limit to one German federal state.

## `postalCodePrefix` (type: `string`):

e.g. "80" for the Munich area or "48147" for one postal code.

## `city` (type: `string`):

Installation location (Ort), e.g. "Münster".

## `commissionedAfter` (type: `string`):

Only installations put into operation after this date (YYYY-MM-DD). Great for finding brand-new systems.

## `commissionedBefore` (type: `string`):

Only installations put into operation before this date (YYYY-MM-DD). Use e.g. 2010-01-01 to find old systems due for repowering or battery retrofits.

## `status` (type: `string`):

Operating, planned, or any status.

## `onlyOrganizations` (type: `boolean`):

Skip installations owned by private persons (their names are anonymised in the register anyway). Keep on for B2B leads.

## `operatorNameContains` (type: `string`):

Filter by operator company name, e.g. "Stadtwerke" or "Solarpark".

## `sortBy` (type: `string`):

Order of results.

## `maxItems` (type: `integer`):

Maximum number of installations to return.

## `includeOperatorContacts` (type: `boolean`):

Fetch each operating company's public register profile: address, email, phone, website, legal form, commercial register number, SME flag. Produces an 'operators' lead list dataset (one row per company).

## Actor input object example

```json
{
  "energyType": "2495",
  "minCapacityKw": 500,
  "state": "",
  "status": "35",
  "onlyOrganizations": true,
  "sortBy": "Bruttoleistung-desc",
  "maxItems": 50,
  "includeOperatorContacts": true
}
```

# Actor output Schema

## `installations` (type: `string`):

One JSON item per solar / battery / wind installation (capacity, location, commissioning date, operator).

## `operators` (type: `string`):

One row per operating company with address, email, phone, website, register number and their installations in this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "energyType": "2495",
    "minCapacityKw": 500,
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("dach_data_tools/mastr-energy-register-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "energyType": "2495",
    "minCapacityKw": 500,
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("dach_data_tools/mastr-energy-register-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "energyType": "2495",
  "minCapacityKw": 500,
  "maxItems": 50
}' |
apify call dach_data_tools/mastr-energy-register-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dach_data_tools/mastr-energy-register-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GrxhWavntkSnLeSKl/builds/E9PFpoi9jm2kk6jwu/openapi.json
