FireDash Public API
FireDash Public API v3. Live fire-hydrant data — hydrant lookup, flow data, operational status, residential account data, and risk-assessment tools — served…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
FireDash Public API v3. Live fire-hydrant data — hydrant lookup, flow data, operational status, residential account data, and risk-assessment tools — served from the FireDash platform.
Endpoints are flat path functions — /hydrants, /v3/status, /risk, /residential, /about, /service — not nested REST resources. An optional version prefix is accepted on every path (/v3/hydrants and /hydrants are the same call).
Authentication — send your API key in the fd-api-key request header. Generate one from the Developer Portal by creating a Consumer Application. /about, /risk, /service, and status reads need no key.
Envelope — every JSON response is wrapped: {"response": } on success (HTTP 200), {"response": {"error": "…"}} on failures (4xx/5xx). Some domain-level failures (e.g. an unknown hydrant id) return HTTP 200 with an errorMessage field inside the envelope instead.
Request formats — GET endpoints read query-string parameters; POST/PATCH endpoints accept either a JSON object body or application/x-www-form-urlencoded fields, interchangeably.
Rate limits — 60 requests/min per IP, 300 requests/min per production API key and 60 requests/min per development key. Over-limit responses are HTTP 429 with a Retry-After header.
Pricing — development keys are free to evaluate with for 1,000 successful requests, or 30 days from an account's first development request, whichever comes first; after that they answer HTTP 402 until the account has an active subscription, which lifts the allowance entirely. The allowance counts calls and days, not bytes, and is per account rather than per application. Within it you may call as fast as the rate limit above permits, and /hydrants returns at most 25 records to a development key. Production usage is metered on the bytes of successful (
Endpoints 9
Hydrants
- GETSearch hydrants (query string)
/hydrantsReturns hydrant records within distance feet of a latitude/longitude pair, nearest first, up to 500 records (25 for a development key). Pass bbox instead of a… - POSTSearch hydrants (request body)
/hydrantsIdentical to the GET form; parameters travel in the request body as JSON or form fields.
Status
- POSTRead a hydrant's operational status
/v3/statusReads the current operational status of one hydrant. No API key required — fhm-v2 served status reads keyless and legacy consumer apps depend on that. An… - PATCHUpdate a hydrant's operational status
/v3/statusSets a hydrant in service (1) or out of service (0). Requires an API key. Marking a hydrant out of service notifies the owning agency's managers by email and…
Risk
- GETRetrieve risk-assessment data
/riskRisk-assessment tool data. No API key required. tool_id=suite (the default) returns the Risk Assessment Suite catalog; tool_id=weather returns weather… - POSTRetrieve risk-assessment data (request body)
/riskIdentical to the GET form; parameters travel in the request body as JSON or form fields.
Residential
- POSTRetrieve a residential account
/residentialReturns a FireDash Residential user's account data — the account record (password withheld) plus the resident's device, hydrant, report, referral, and survey…
Service
- GETAPI and application information
/aboutService metadata. No API key required. - GETLiveness probe
/serviceReturns the plain-text body 1 when the API is up. Used by monitors and uptime probes. No API key required, no JSON envelope.
API details
- Base URL
https://api.firedash.ushttps://firedash.us/api- Authentication
- An API key in the fd-api-key header
- Operations
- 9 operations on 6 pathsGET 4POST 4PATCH 1
- Main resources
- Hydrants 2Risk 2Service 2Status 2Residential 1
- Response formats
application/jsontext/plain- Description format
- OpenAPI 3.0.3, API version
3.0.0 - Links
- OpenAPI document · Terms of service · Support
- Listed from
- Firedash's published OpenAPI description
How to test the FireDash Public API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the FireDash Public API collection, without the publisher's secrets.
- Add your credentialsThis API uses an API key in the fd-api-key header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Search hydrants (query string)” (GET /hydrants), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the FireDash Public API?
FireDash Public API v3. Live fire-hydrant data — hydrant lookup, flow data, operational status, residential account data, and risk-assessment tools — served… It is listed under Developer tools and has 9 endpoints.
Who publishes the FireDash Public API?
It is listed from FireDash's public API description (an OpenAPI document), not published by FireDash on Swastik Codes. Anyone who controls firedash.us can claim the profile by adding a DNS TXT record.
What is the base URL of the FireDash Public API?
Its description lists 2 base URLs: https://api.firedash.us, https://firedash.us/api. The first is the usual one; the others are typically sandbox or regional servers.
How do I authenticate with the FireDash Public API?
With an API key in the fd-api-key header.
How many endpoints does the FireDash Public API have?
9 operations on 6 paths (4 GET, 4 POST, 1 PATCH). The largest groups are Hydrants, Risk, Service, Status.
Is forking the FireDash Public API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.