Last updated: 19 April 2026
EmergencyAPI is operated by SEY Solutions (ABN 13 531 353 123), a registered Australian business.
We aggregate real-time emergency incident and warning data from 28 official Australian government feeds plus national sources (Geoscience Australia, satellite hotspot data) into a single standardised API.
Under the Australian Institute for Disaster Resilience (AIDR) framework, EmergencyAPI is classified as a "Privately owned warning publisher or disseminator". The same category includes global digital platforms (Google, Facebook), insurers providing customer alerts, and private weather services.
This designation was confirmed in a formal reply from Dr Richard Hammond, Senior Policy Officer and CAP-AU Custodian at the Bureau of Meteorology, on 16 April 2026. AIDR publishes a guidance document for operators in our category, the Warnings Republishers Companion (AIDR 2021, CC BY 4.0), which lists twelve operational obligations.
This page documents our posture against each of those obligations, plus adjacent concerns (CAP-AU standards alignment, agency engagement, data licensing, security, privacy) that matter to customers evaluating us.
Our self-audit against the twelve obligations in the AIDR Warnings Republishers Companion, reviewed as of 19 April 2026:
| # | Obligation | Status |
|---|---|---|
| 1 | Establish prior relationship with statutory provider (MoU or informal) | Partial |
| 2 | Platform robust under high demand | Satisfied |
| 3 | Warnings are current and republished in a timely manner | Satisfied |
| 4 | Preserve intent of warning (wording and spatial representation) | Partial |
| 5 | Include original source, date, and time of publication | Satisfied |
| 6 | Republish revisions, updates, and de-escalations | Partial |
| 7 | Indicate unofficial sources clearly | Satisfied |
| 8 | Verify unofficial information against official sources | Partial |
| 9 | Remove, retract, or correct inaccurate content promptly | Partial |
| 10 | CAP-AU-STD compliance consideration | Satisfied |
| 11 | Comply with relevant legislation, regulations, privacy and data laws | Satisfied |
| 12 | Understand legal responsibilities and liability as a republisher | Satisfied |
Summary: 7 fully satisfied, 5 partial. Closure work on the remaining obligations is actively underway (certainty-field audit, explicit upstream-cancellation detection, unofficial-source cross-check policy, retraction mechanism).
EmergencyAPI is designed to conform to OASIS Common Alerting Protocol (CAP) v1.2, the international XML standard for public warning messages, and its Australian profile (CAP-AU-STD, maintained by the Bureau of Meteorology).
?format=cap-au on the incidents endpoint.We maintain a transparent paper trail of our engagement with every agency whose data we consume. Customers can verify our standing directly with the relevant agency using the contacts below.
| Agency / Body | Jurisdiction | Status | Basis |
|---|---|---|---|
| WA DFES | Western Australia | Approved | Commercial use approved by Tim Vella (Project Manager, NextGen Warnings Project, DFES) on 15 April 2026. SLIP designated-feed access granted 16 April 2026. |
| BOM CAP-AU Custodian | Commonwealth | Engaged | Formal correspondence with Dr Richard Hammond, Senior Policy Officer. Governance-level engagement on CAP-AU alignment and republisher status, ongoing since 14 April 2026. |
| NT PFES | Northern Territory | Progressing | NT Open Data team responded 17 April 2026 confirming they are making internal enquiries with the PFES business area regarding our use. |
| QLD QFD | Queensland | Open licence | Queensland Fire Department data published under Creative Commons Attribution 4.0 (CC BY 4.0). Commercial use explicitly permitted. Attribution satisfied via our /api/v1/attribution endpoint. |
| ACT ESA | Australian Capital Territory | Open licence | ACT Emergency Services Agency data published under CC BY 4.0. Commercial use explicitly permitted. |
| Geoscience Australia | Commonwealth | Open licence | GA earthquake data published under CC BY 4.0. National seismology data explicitly open for commercial use. |
| NSW RFS | New South Wales | Pending reply | Written request for commercial redistribution permission sent to NSW Rural Fire Service media mailbox on 13 April 2026. Awaiting reply. AIDR Warnings Republishers framework referenced in the request. |
| VIC EMV | Victoria | Pending reply | Developer-access application sent to Emergency Management Victoria on 13 April 2026. Awaiting reply. VIC EMV data is CC BY 3.0 AU once access is granted. |
| SA SAFECOM | South Australia | Pending reply | Commercial licence request sent to SAFECOM on 13 April 2026 covering CFS, MFS, and SES agency feeds. Awaiting reply. |
| TAS TasALERT | Tasmania | Pending reply | Licensing clarification request sent to TasALERT on 13 April 2026. Underlying data is CC BY 4.0. Awaiting written acknowledgement. |
| AIDR (AFAC) | National | Pending reply | Introduction as a republisher and AWS hazard-icon usage inquiry prepared. Sending imminently. |
Full per-source attribution, including the licence under which each feed is provided and whether the source is an official statutory agency or a community-decoded feed, is available at our attribution endpoint:
emergencyapi.com/api/v1/attribution
Every source carries an official: boolean flag. Statutory government feeds return true. A small number of community-decoded sources (SA pager dispatches via urgmsg.net, which decode public GRN radio transmissions under the Australian Radiocommunications Act) return false. Customers who need statutory-only data can filter on that flag.
We comply with the Australian Privacy Act 1988. Our full Privacy Policy is at /privacy, including how we collect, store, and protect account information and API usage data.
Our Terms of Service at /terms include warnings-republisher-specific clauses aligned with the AIDR framework, including:
This page is reviewed quarterly. The next scheduled review is 19 July 2026. Re-audit is also triggered by:
For procurement, compliance verification, or partnership conversations: