Reference · built on requestCommons signalHazards & public safety

Seattle Real Time Fire 911 Calls

Seattle Fire Department 911 dispatches with response type, time, address, and location, updated every 5 minutes on data.seattle.gov.

Request accessPricing ↗

About

The City of Seattle publishes Seattle Fire Department 911 dispatches as dataset kzjm-xkqj on its Socrata open data portal, data.seattle.gov. The dataset description reads: provides Seattle Fire Department 911 dispatches, updated every 5 minutes. Each row is one dispatch with an address, a response type, a call date and time, latitude and longitude, a report location point, and an incident number. The portal exposes it through the SODA API as JSON, CSV, or GeoJSON, with SoQL query parameters such as $limit and $order.

On Fibric, an operator watches for dispatches at or near the addresses you run and proposes a check-in, a roster pull, or an incident record for your approval, with the incident number attached.

This is a reference listing. It documents what Fibric would read from Seattle Real Time Fire 911 Calls and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Each dispatch row: Address (Location of Incident), Type (Response Type), Datetime (the date and time of the call), and Incident Number
  • Latitude, Longitude, and Report Location, a point column that returns a GeoJSON Point in JSON output
  • Computed region columns: Zip Codes, City Council Districts, 2010 Census Tracts, SPD Beats, and SPD Micro Community Policing Plan Areas
  • The resource endpoint /resource/kzjm-xkqj in .json, .csv, or .geojson, filtered and ordered with SoQL parameters such as $order=datetime DESC
  • Dataset metadata: update frequency Near Realtime, category Public Safety, license Public Domain, and a rowsUpdatedAt stamp

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Confirm a fire panel alarm against a real dispatch

    When your building's fire panel reports trouble or alarm, the operator queries the last minutes of dispatches for your Address and proposes either a stand-down note or an escalation, citing the Incident Number.

    With Fire Panel Trouble

  • Pull the evacuation roster when SFD is dispatched to your site

    A new row whose Address matches a site you run triggers a proposal to assemble the roster of people on site, sent to your safety lead to approve.

    With Evacuation Roster

  • Keep field crews clear of active incidents

    Dispatches near a crew's next stop, matched on Latitude and Longitude, prompt the operator to propose a resequenced route or a delay, with the dispatch Type and time attached.

    With Field Dispatch

  • Start an incident record from the dispatch

    For a dispatch at your address, the operator drafts an incident record pre-filled with Datetime, Type, and Incident Number for your review.

    With Incident Draft

Requirements

  • A Socrata app token if you poll steadily; without one, requests share an IP-based throttle and can return 429
  • A polling interval that matches the five-minute update cycle the dataset description states
  • The addresses or coordinates of your sites, to filter rows by Address or by Latitude and Longitude
  • Paging with $limit and $offset for history; $limit defaults to 1,000 rows per request
Authentication
No key is required. Requests without a Socrata app token are throttled by IP from a shared pool; an app token registered in a Socrata profile and sent as the X-App-Token header lifts that throttle.

Limits

  • Rows carry the dispatch address, type, time, and incident number only; no units, outcome, closure time, or narrative
  • The description says updated every 5 minutes and the metadata says Near Realtime; the city states no latency guarantee
  • Type is described only as Response Type; the metadata publishes no list of its values
  • Unauthenticated requests are throttled from a shared pool, and SODA 3.0 endpoints require an app token or authentication

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Seattle Real Time Fire 911 Calls ↗

Questions and answers

What does the endpoint look like?
https://data.seattle.gov/resource/kzjm-xkqj.json, with .csv or .geojson for other formats. SoQL parameters such as $limit and $order go in the query string; $limit defaults to 1,000 rows. Socrata's 3.0 API uses /api/v3/views/kzjm-xkqj/query.json and requires an app token or authentication.
How fresh is the data?
The dataset description says updated every 5 minutes, and the metadata update frequency reads Near Realtime. Each row's Datetime is the date and time of the call. The city publishes no stated delay between dispatch and publication.
What license applies?
The dataset metadata lists the license as Public Domain, attributed to the City of Seattle and published by data.seattle.gov. The contact listed for the dataset is open.data@seattle.gov.
Ask about Seattle Real Time Fire 911 Calls

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by City of Seattle, Seattle Fire Department dispatches (data.seattle.gov). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy