Bicycle accidents

Open data API in a single place

Provided by Koumoul

Get early access to Bicycle accidents API!

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

Dataset information

Country of origin
Updated
2026.01.28 14:23
Created
2019.08.16
Available languages
English
Keywords
accident, circulations, velo
Quality scoring

Dataset description

This dataset was built on the basis of the [body accident database] (https://www.data.gouv.fr/en/datasets/base-de-donnees-accidents-corporels-de-la-circulation) (accidents occurring on a road open to public traffic, involving at least one vehicle and resulting in at least one victim requiring care) for the period 2005-2022. It identifies accidents in which at least **one person on a bicycle** has been involved. The seizures of information describing the accident were made by the police unit (police, gendarmerie, etc.) which intervened at the scene of the accident. These seizures are collected in a sheet entitled ‘Injury Analysis Bulletin’. All these forms constitute the national register of road traffic injuries, known as the ‘BAAC file’, administered by the National Interministerial Observatory for Road Safety (ONISR). Unlike the source data separated into 4 files, we grouped the data into a single file where each line corresponds to a person. The same accident can therefore correspond to several lines, for example, if several people are present on the bike (e.g. child seat), or if several bicycles were involved in the same accident (e.g. fall into a platoon). We have omitted some original fields, added others by calculation, and sometimes made transformations on formats. The data codes have also been replaced by their corresponding values in the variable dictionary.
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.

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

Copyright © 2026. Made by Apitalks