FireWatchPro
API access

Your fire-watch records, in your own system.

Marshals and dispatch managers keep a second set of books because the records live in someone else’s app. That’s tedious, and it’s where things get missed. The FireWatchPro API is a read-only feed of everything your account can already see — watches, patrol records, signed reports, alerts, events — so your RMS, dashboard, or spreadsheet stays current without anyone retyping.

Getting a key

Keys are created in the console, scoped to one account, shown once.

Fire watch companies

Company → Billing & API → API access. Company admins only. Your key sees your watches, your guards’ shifts, your reports and alerts, and your events.

AHJs & fire marshals

AHJ → Settings → API access. Your key sees every watch, order, shift, report, alert, impairment, and event in your jurisdiction, across all companies.

Security

Keys look like fwp_live_…. We store only a SHA-256 hash; the full key is shown once. Revoke any time. Scopes limit a key to watches, reports, alerts, or events. Up to 10 active keys per account. Read-only — nothing in the API can change a record.

Reference

Endpoint reference

Base URL https://api.firewatchpro.com/v1. Send the key as a Bearer token. Responses are JSON. Timestamps are Unix milliseconds unless the field is an ISO date string. Pagination: pass since (or after_id for watches) from the previous page’s next_since / next_after_id; limit defaults to 100, max 500.

curl -H "Authorization: Bearer fwp_live_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  "https://api.firewatchpro.com/v1/shifts?since=1760000000000&limit=200"
EndpointScopeReturnsFilters
GET /v1/meanyThe key, its scopes, and the company or jurisdiction it belongs to.—
GET /v1/watches
GET /v1/watches/{id}
read:watchesCompany-scheduled fire watches: site, reason, impaired system, interval, assigned guard, shift and report counts. Detail adds the shifts.status, after_id, limit
GET /v1/ordersread:watchesAHJ-issued fire watch orders with requirements, responsible party, issue/close times.status, since, limit
GET /v1/shifts
GET /v1/shifts/{id}
read:watchesGPS-verified patrol records: start/end, checkpoint and ping counts, consecutive misses, guard, site. Detail adds checkpoints (time, location-verified flag, note, photo flag) and hazards. Raw GPS trails are not exposed.since, watch_id, limit
GET /v1/reportsread:reportsSigned shift reports with hash, delivery flags, a pdf_url that works for 30 days, and a public verify_url.since, limit
GET /v1/alertsread:alertsPatrol alerts: reminder, missed, escalated, resolved — with minutes late and consecutive count.kind, since, limit
GET /v1/impairmentsread:watchesImpairment reports and their restoration status.status, since, limit
GET /v1/eventsread:eventsCrowd-manager events with required, assigned, cleared, and checked-in counts.since, limit
GET /v1/openapi.jsonnoneMachine-readable OpenAPI 3.0 description of the above.—

Errors

401 missing or unknown key · 403 key lacks the scope · 404 record not found or outside the key’s account. Error bodies follow RFC 7807 (title, status, detail).

Polling

Poll each collection with since on a schedule that fits your system (every 5–15 minutes is plenty). Store the returned next_since. There is no hard rate limit today; keep it under 60 requests a minute per key and we’ll never need one.

Need a webhook, a write endpoint, or a Brycer / ImageTrend connector? Tell us what your system needs — the read API ships first because it’s what every records system asked for.

Stop retyping fire-watch records.

Create a key in your console today. Included with Enterprise and on every AHJ account; Starter and Pro keys work during the rollout, and we will give notice before that changes.