Development of accidents at work absolute and each 1,000 full-time workers from 1960 onwards

Open data API in a single place

Provided by Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA); Fb 6.2 Veröffentlichungen, Internet

Get early access to Development of accidents at work absolute and each 1,000 full-time workers from 1960 onwards API!

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

Dataset information

Catalog
Bundesanstalt für Arbeitsschutz und Arbeitsmedizin (BAuA); Fb 6.2 Veröffentlichungen, Internet catalog
Country of origin
Germany
Updated
2021.03.26 15:16
Created
2018.04.15
Available languages
English
Keywords
Arbeitsunfälle, Tödliche Arbeitsunfälle, Neue Arbeitsunfallrenten, Meldepflichtige Arbeitsunfälle
Datasource
Official portal for European data link
Quality scoring

Dataset description

The table contains analyses of data on the development of accidents at work in absolute terms and per 1,000 full-time workers (reportable accidents at work, new occupational accidents, fatal accidents at work) from 1960 onwards. All data on accidents at work, except data on new occupational accident pensions, are presented differentiated by accident insurance institutions (commercial professional associations, agricultural professional association, accident insurance institution of the public sector). Source: Accident insurance institution
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.storeBuilt by Apitalks

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

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks