--- title: "IPAWS Archived Alerts" method: GET path: "/v1/IpawsArchivedAlerts" tags: ["Emergency Management/Preparedness/Alerts"] --- # IPAWS Archived Alerts `GET /v1/IpawsArchivedAlerts` ## Request - Base URL: `https://www.fema.gov/api/open` - URL: `https://www.fema.gov/api/open/v1/IpawsArchivedAlerts` - Auth: none declared - TypeScript: (a function with typed inputs; its response is checked against the schema) The Integrated Public Alert and Warning System (IPAWS) is a modernization of the nation's alert and warning infrastructure that unifies the United States' Emergency Alert System (EAS), Wireless Emergency Alerts (WEA), the National Oceanic and Atmospheric Administration (NOAA) Weather Radio, and other public alerting systems implemented as a set of Web services. IPAWS was designed to modernize these systems by enabling alerts to be aggregated over a network and distributed to the appropriate system for public dissemination. Organized and managed by FEMA, the system supports alert origination by Federal, state, local, territorial and tribal officials, and subsequent dissemination to the public using a range of national and local alerting systems. This data set contains recent*, historic, and archived IPAWS Common Alerting Protocol (CAP) v1.2 messages from June 2012 to the present including date, time, event code (examples listed below), city, county, joint agency, police, law enforcement, Collaborative Operating Group (COG), State(s), locality, territory or tribe. It can be used to capture and analyze historic and archived messages. *The dataset is published with a twenty-four (24) hour delay to reduce the risk of being confused with an active alert received from the live IPAWS feed. The most recent record will reflect the alert(s) sent twenty-four (24) hours ago (if such records exist). For example, if an alert originator sent an alert at 1459GMT on June 1st and sent a different alert at 1600GMT on June 2nd, these alerts will not be visible in the dataset until 1459GMT on June 2nd and 1600GMT June 3rd respectively. Information on signing up for receiving active alerts can be found at https://www.fema.gov/emergency-managers/practitioners/integrated-public-alert-warning-system . To request access to alerts issued through IPAWS or for a list of companies with access to the IPAWS All-Hazards Information Feed, email ipaws@fema.dhs.gov. The data elements within the CAP messages are well documented and can be found in the following technical document: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf See also: IPAWS Overview - https://www.fema.gov/emergency-managers/practitioners/integrated-public-alert-warning-system This is raw, unedited data with no personally identifiable information from the IPAWS Alert Aggregator from June 2012 to the present created by over 1450 Alert Originators across the country. FEMA does not validate the content of each message. As such, it may contain a small percentage of human error. OpenFEMA does not have a full backup capability so if the site goes down, the information will be inaccessible. This is a rare occurrence. Earlier messages may contain non-compliant geocoordinates. Recent versions of the software check these coordinates for compliance. This dataset is not intended to be an official federal report and should not be considered an official federal report. If you are using this site for other than research purposes, please understand that these CAP messages are captured only after the official IPAWS message has been sent. Note that the original IPAWS CAP message is provided in the originalMessage element of the returned JSON object. The XML based message is encoded such that a separate tool, such as a JSON parser, computer language, or browser must be used to view the original format. If no such tool is available to you, online utilities exist, such as https://codebeautify.org/json-escape-unescape that will decode the message. See the originalMessage field description for additional details. Due to its size and its hierarchical data structure, working with the IPAWS Archived Alerts file can be challenging. See the OpenFEMA Guide to Working with Large Data Sets page for useful hints and tips: https://www.fema.gov/about/openfema/working-with-large-data-sets . The Developer Resources page has sample IPAWS API queries in the section called IPAWS Archived Alerts Query Examples: https://www.fema.gov/about/openfema/developer-resources If you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov. IPAWS specific queries should be directed to IPAWS@fema.dhs.gov. ## Query parameters - `$filter` string - `$top` integer - `$skip` integer - `$count` boolean - `$filename` string - `$metadata` boolean - `$gzip` boolean - `$orderby` string[] - `$select` string[] - `$format` 'json' | 'jsonl' | 'jsona' ## Response `200` OK - object - `metadata` Metadata - `skip` number, nullable - `filter` string, nullable - `orderBy` string, nullable - `select` string, nullable - `rundate` string, nullable - `top` number, nullable - `format` string, nullable - `metadata` boolean, nullable - `entityname` string - `version` string - `url` string - `count` number, nullable - `IpawsArchivedAlerts` V1IpawsArchivedAlerts[] - `id` string, string: Unique ID assigned to the record - `identifier` string, string: The identifier of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `sent` string, date-time: The time and date of the origination of the alert message. Note that the original CAP message sent date defines a UTC offset and that OpenFEMA converts this date to UTC Zulu time. If you need the exact representation of the sent data as it appears in the CAP message, see the Original XML Message field. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `sender` string, string: The identifier of the sender of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `status` string, string: The code denoting the appropriate handling of the alert message. Code Values: Actual - Actionable by all targeted recipients; Exercise - Actionable only by designated exercise participants; exercise identifier SHOULD appear in ; System -For messages that support alert network internal functions. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `msgType` string, string: The code denoting the nature of the alert message. Code Values: Alert -Initial information requiring attention by targeted recipients; Update -Updates and supersedes the earlier message(s) identified in ; Cancel - Cancels the earlier message(s) identified in ; Ack -Acknowledges receipt and acceptance of the message(s) identified in . For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `source` string, string, nullable: The text identifying the source of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `scope` string, string: The code denoting the intended distribution of the alert message. Code Values: Public - For general dissemination to unrestricted audiences. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `restriction` string, string, nullable: The text describing the rule for limiting distribution of the restricted alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `addresses` string, string, nullable: The group listing of intended recipients of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `code` object[], nullable: The code denoting the special handling of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `note` string, string, nullable: The text describing the purpose or significance of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `incidents` string, string, nullable: The group listing naming the referent incident(s) of the alert message. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf - `searchGeometry` object, nullable: This field includes the GeoJSON of all of the well-formed geometries found in the info.area fields (polygon and circle). This field is included to facilitate geospatial queries to find alerts - `infos` object[], nullable - `cogId` number: The COG Identifier Associated with the COG Profile - `xmlns` string, string: Name space for the XML MessagE - `originalMessage` string, string: The container for all component parts of the alert XML message. Please note that the original XML message as delivered by the API in a JSON format contains encoded content. That is, certain characters, double quotes for example, are escaped such that the original format is preserved. This content can be decoded with JSON parsers, computer languages, and some web browsers to see the raw XML format. For additional information on the metadata, please see the IPAWS Data Dictionary URL: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf --- [API](https://skmtc.dev/fema/apis/openfema-api.md) - [All operations](https://skmtc.dev/fema/apis/openfema-api/llms.txt) - [OpenAPI document](https://skmtc.dev/fema/apis/openfema-api/revisions/fdc02603897f?raw)