Combustion plants according to 44. BImSchV Hamburg

Open data API in a single place

Provided by Behörde für Umwelt, Klima, Energie und Agrarwirtschaft (BUKEA)

Get early access to Combustion plants according to 44. BImSchV Hamburg API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Behörde für Umwelt, Klima, Energie und Agrarwirtschaft (BUKEA) catalog

Country of origin

Germany

Updated

2026.02.19 17:13

Created

2026.02.18

Available languages

English

Keywords

geodaten

Datasource

Official portal for European data link

Quality scoring

Dataset description

Individual firing systems within the scope of 44. BImSchV (medium-sized combustion plants, e.g. boilers, gas turbine and internal combustion engine plants), which have a rated thermal input of equal to or more than 1 MW, according to § 6 of the 44. BImSchV is subject to registration and must be notified to the competent authority. The obligation applies directly to the operator of installations falling within the scope of 44. BImSchV fall. Further information on the obligation to report in Hamburg can be found on the Hamburg website at 44. BImSchV described: https://www.hamburg.de/ Fachthemen/15025250/44bimschv/

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service