Skip to main content

Deepfire OGC API

Public, read-only access to Deepfire's satellite wildfire data: fire detections (hotspots), candidate fires (clusters), and estimated fire perimeters — current and historical, global coverage.

No API key needed

All endpoints are public. No signup, no authentication, no API key.

Two standards, same data

Base URLUse it for
OGC API - Features (recommended)https://ogc.deepfire.co/ogc/features/v1Modern REST/JSON integrations
WFS 2.0https://ogc.deepfire.co/owsExisting GIS tooling (QGIS, ArcGIS), server-side sorting, feature counts

CORS is open (Access-Control-Allow-Origin: *), so you can call the API from browser JavaScript as well as from a backend — and the Send API Request buttons in the API reference work right in the page.

Collections

CollectionContentsGeometryApprox. scale
deepfire:hotspotsSatellite fire detectionsPoint~18.7M rows, ~380k active
deepfire:clustersCandidate fires (cluster centroids)Point~3.25M rows
deepfire:satellite-perimetersEstimated fire perimeter snapshotsMultiPolygon~140k snapshots, ~19k active

All geometries are EPSG:4326, lon/lat order.

The active flag

Every collection serves the full history — current and past rows — and an unfiltered query returns everything. The boolean active attribute distinguishes the live working set (active = true) from historical rows. If you only want live fires, filter active = true yourself — see Filtering.

Freshness

New detections are ingested from the upstream satellite programs about every minute, perimeters are recomputed about every 30 seconds, and responses are edge-cached for 60 seconds — so what you see can lag ingestion by roughly one to two minutes. Details in Data sources & update cadence.

Where next

  • Quickstart — first requests in two minutes.
  • Collections — what each collection contains, attribute by attribute.
  • Guides — filtering, paging & bulk export, output formats, WFS, limits.
  • API Reference — every endpoint, with runnable request panels.