Incidents attended by LFB, by type and borough

Open data API in a single place

Provided by LFB Information Management

Get early access to Incidents attended by LFB, by type and borough API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
special-services, lfb, rescue, casualties, fire, false-alarms, attended, safestats, indicents, lfb-performance, lfepa
Quality scoring

Dataset description

<p>London Fire Brigade (LFB) data covering all incidents attended by month back to January 2013, broken down by incident type:</p> <ul> <li>All fires attended - broken down by primary* and secondary fires</li> <li>Deliberate fires attended</li> <li>Dwelling &amp; non-dwelling fires attended</li> <li>False alarms attended</li> <li>Road Traffic Accidents attended</li> <li>Vehicle fires attended - broken down by deliberate/accidental/unknown</li> <li>Open space fires attended - broken down by deliberate/accidental/unknown</li> <li>Rubbish fires attended - broken down by deliberate/accidental/unknown</li> <li>Shut-in-lifts attended</li> <li>Special services - non-emergency visits</li> </ul> <p>*Primary fires comprise of all fires attended by LFB in buildings, vehicles and outdoor structures, and fires involving casualties, and fires attended by five or more appliances.&nbsp;</p> <p>The statistics include some incidents that are not geo-referenced (with a borough name). Sometimes incidents are geo-coded later, and so the data can change each month, and data for more recent periods must be regarded as provisional.</p> <p> <span>Data are available in raw machine-readable (csv) format.</span> </p>
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