Requesting Active Hazards

To request the list of current active hazards please use the route defined here:

Get active hazards

GET https://api.disasteraware.com/hazards/active

Headers

Name	Type	Description
Authorization	string	Authorize to access the API.

200

[
    {
        "app_ID": 0,
        "app_IDs": "",
        "autoexpire": "Y",
        "category_ID": "EVENT",
        "charter_Uri": "",
        "comment_Text": "354006",
        "create_Date": "1556403824755",
        "creator": "DisasterAWARE (Automated)",
        "end_Date": "1622491650058",
        "glide_Uri": "",
        "hazard_ID": 98602,
        "hazard_Name": "Volcano - Sabancaya, Peru",
        "last_Update": "1622060308701",
        "latitude": -15.78,
        "longitude": -71.85,
        "master_Incident_ID": "130.1622059574931.1",
        "message_ID": "130.1622059574931",
        "org_ID": -1,
        "severity_ID": "WARNING",
        "snc_url": "https://hazardbrief.pdc.org/PRODUCTION/ui/index.html?uuid=4a6bea66-a0be-4675-9c28-246ebb71736b",
        "start_Date": "1556403900000",
        "status": "A",
        "type_ID": "VOLCANO",
        "update_Date": "1622059652662",
        "update_User": null,
        "product_total": "10008",
        "uuid": "4a6bea66-a0be-4675-9c28-246ebb71736b",
        "in_Dashboard": "",
        "areabrief_url": null,
        "description": "Volcanic activity has been reported for Sabancaya in Peru, by the Volcanic Ash Advisory Centre (VAAC) BUENOS AIRES on May 26, 2021, 20:15:00 GMT.\n\nThis volcanic activity is reported based on aerial, satellite and/or ground observations.\nBased on the limited data available, it is estimated that 571 people,  127 households, and $7.56 Million (USD) of infrastructure* are within 10 km (6 miles) and more likely to be adversely impacted, and that 13,426 people, 2,984 households, and $178 Million (USD) of infrastructure* are 10-30 km (6-18 miles) from the volcano. Additional information will be provided as it becomes available by official sources.\n\nVolcano information sources for this report include: GOES-E. WEBCAM. VOLCAT. \n*The cost represents the total replacement value of the infrastructure.\n",
        "roles": []
    },
    {
        "app_ID": 0,
        "app_IDs": "",
        "autoexpire": "Y",
        "category_ID": "EVENT",
        "charter_Uri": "",
        "comment_Text": "6ef316b0-d6c7-479a-8ea2-bbad0afa2765",
        "create_Date": "1622059680000",
        "creator": "DisasterAWARE (Automated)",
        "end_Date": "1622232480000",
        "glide_Uri": "",
        "hazard_ID": 135935,
        "hazard_Name": "Civil Unrest (Protest) - Sohar, Oman",
        "last_Update": "1622060305432",
        "latitude": 24.35,
        "longitude": 56.732,
        "master_Incident_ID": "125.1622059846214.1",
        "message_ID": "125.1622059846214",
        "org_ID": -1,
        "severity_ID": "INFORMATION",
        "snc_url": "https://hazardbrief.pdc.org/PRODUCTION/ui/index.html?uuid=8b0f6557-f170-4694-8956-01e00007a312",
        "start_Date": "1622059680000",
        "status": "A",
        "type_ID": "CIVILUNREST",
        "update_Date": "1622059870693",
        "update_User": null,
        "product_total": "2",
        "uuid": "8b0f6557-f170-4694-8956-01e00007a312",
        "in_Dashboard": "",
        "areabrief_url": null,
        "description": "A Civil Unrest incident (a protest) was reported in Sohar, Oman on May 26, 2021. \n Preliminary reports indicate there were no casualties.  \n\nEvent Summary*: Protests in Sohar continued over the economic situation on Wednesday and police fired teargas to disperse them.  Protesters responded by throwing rocks at them. \n(* \"Event Summary\" provided by GeoPioneer/AP.) \n",
        "roles": []
    },
    {
        "app_ID": 0,
        "app_IDs": "",
        "autoexpire": "Y",
        "category_ID": "EVENT",
        "charter_Uri": "",
        "comment_Text": "TORNADO-WATCH-2021-209-KICT",
        "create_Date": "1622060011138",
        "creator": "DisasterAWARE (Automated)",
        "end_Date": "1622080800000",
        "glide_Uri": "",
        "hazard_ID": 135936,
        "hazard_Name": "Tornado - Wichita, KS WFO Region, US",
        "last_Update": "1622060182225",
        "latitude": 38.5293,
        "longitude": -98.1972,
        "master_Incident_ID": "1051.317131.811305.1",
        "message_ID": "1027.1622059951708",
        "org_ID": -1,
        "severity_ID": "WATCH",
        "snc_url": "https://hazardbrief.pdc.org/PRODUCTION/ui/index.html?uuid=4e606dcd-0946-4fb2-8cac-68c213b8c706",
        "start_Date": "1622059860000",
        "status": "A",
        "type_ID": "TORNADO",
        "update_Date": "1622060011057",
        "update_User": null,
        "product_total": "2",
        "uuid": "4e606dcd-0946-4fb2-8cac-68c213b8c706",
        "in_Dashboard": "",
        "areabrief_url": null,
        "description": "Latest NWS Summary\nWeather Forecast Office: Wichita, KS (KICT)\nEvent Tracking Number: 209\n\nTHE NATIONAL WEATHER SERVICE HAS ISSUED TORNADO WATCH 209 IN\nEFFECT UNTIL 9 PM CDT THIS EVENING FOR THE FOLLOWING AREAS\n\nIN KANSAS THIS WATCH INCLUDES 8 COUNTIES\n\nIN CENTRAL KANSAS\n\nBARTON                ELLSWORTH             LINCOLN\nMCPHERSON             RICE                  RUSSELL\nSALINE\n\nIN SOUTH CENTRAL KANSAS\n\nRENO\n\nTHIS INCLUDES THE CITIES OF ELLSWORTH, GREAT BEND, HUTCHINSON,\nLINCOLN, LYONS, MCPHERSON, RUSSELL, SALINA, STERLING,\nSYLVAN GROVE, AND WILSON.",
        "roles": []
    },
    {
        "app_ID": 0,
        "app_IDs": "",
        "autoexpire": "Y",
        "category_ID": "EVENT",
        "charter_Uri": "",
        "comment_Text": "TORNADO-WARNING-2021-6-KDDC",
        "create_Date": "1622059538256",
        "creator": "DisasterAWARE (Automated)",
        "end_Date": "1622065500000",
        "glide_Uri": "",
        "hazard_ID": 135934,
        "hazard_Name": "Tornado - Dodge City, KS WFO Region, US",
        "last_Update": "1622060137720",
        "latitude": 38.754,
        "longitude": -99.1574,
        "master_Incident_ID": "1051.317128.811301.1",
        "message_ID": "1027.1622059711387",
        "org_ID": -1,
        "severity_ID": "WARNING",
        "snc_url": "https://hazardbrief.pdc.org/PRODUCTION/ui/index.html?uuid=d9801984-ec8b-443f-abfc-c0d506956370",
        "start_Date": "1622059320000",
        "status": "A",
        "type_ID": "TORNADO",
        "update_Date": "1622059763784",
        "update_User": null,
        "product_total": "4",
        "uuid": "d9801984-ec8b-443f-abfc-c0d506956370",
        "in_Dashboard": "",
        "areabrief_url": null,
        "description": "Latest NWS Summary\nWeather Forecast Office: Dodge City, KS (KDDC)\nEvent Tracking Number: 6\n\nAt 306 PM CDT, a confirmed tornado was located near Munjor, moving\neast at 10 mph.\n\nHAZARD...Damaging tornado and tennis ball size hail.\n\nSOURCE...Radar confirmed tornado.\n\nIMPACT...Flying debris will be dangerous to those caught without\nshelter. Mobile homes will be damaged or destroyed. Damage\nto roofs, windows, and vehicles will occur.  Tree damage is\nlikely.\n\nLocations impacted include...\nPfeifer and Munjor.\n\nPRECAUTIONARY/PREPAREDNESS ACTIONS...\n\n To repeat, a tornado is ongoing. TAKE COVER NOW! Move to a basement\nor an interior room on the lowest floor of a sturdy building. Avoid\nwindows. If you are outdoors, in a mobile home, or in a vehicle, move\nto the closest substantial shelter and protect yourself from flying\ndebris.",
        "roles": []
    }
]

403

Invalid Token

See Authorizing Requests page to get your accessToken.

cURL

curl --location --request GET \
  'https://api.disasteraware.com/hazards/active' \
  --header 'Authorization: Bearer your_accessToken'

Java

import java.io.IOException;
import java.io.InputStream;
import java.net.HttpURLConnection;
import java.net.URL;
import java.util.Scanner;

class Main {

	public static void main(String[] args) throws IOException {
		URL url = new URL("https://api.disasteraware.com/hazards/active");
		HttpURLConnection httpConn = (HttpURLConnection) url.openConnection();
		httpConn.setRequestMethod("GET");

		httpConn.setRequestProperty("Authorization", "Bearer your_accessToken");

		InputStream responseStream = httpConn.getResponseCode() / 100 == 2
				? httpConn.getInputStream()
				: httpConn.getErrorStream();
		Scanner s = new Scanner(responseStream).useDelimiter("\\A");
		String response = s.hasNext() ? s.next() : "";
		System.out.println(response);
	}
}

Node.js

var fetch = require('node-fetch');

fetch('https://api.disasteraware.com/hazards/active', {
    headers: {
        'Authorization': 'Bearer your_accessToken'
    }
});

PHP

<?php
include('vendor/rmccue/requests/library/Requests.php');
Requests::register_autoloader();
$headers = array(
    'Authorization' => 'Bearer your_accessToken'
);
$response = Requests::get('https://api.disasteraware.com/hazards/active', $headers);

Python

import requests

headers = {
    'Authorization': 'Bearer your_accessToken',
}

response = requests.get('https://api.disasteraware.com/hazards/active', headers=headers)

The response will include an array of objects that reflect the currently active hazards in the system. Each element in the array will include the following properties:

Properties	Definitions
app_ID	This is probably safe to ignore. This represents the application that created the hazard. Hazards are federated and can be synchronized by different versions of DisasterAWARE. In DAE most hazards will have an app_ID of 0. This means that the hazard was created by the “data core” or central processing for hazards. Hazards created by users or automated processes specific to an instance of DisasterAWARE will carry the application id of that system. Systems can set up rules for synchronization with other systems e.g. to share or not share hazards created within that environment.
app_IDs	Deprecated.
autoexpire	Indicates whether or not the hazard will automatically expire. There are different rules for how long a hazard shall persist.
category_ID	The category of this hazard e.g. EVENT, RESPONSE.
charter_Uri	Deprecated. Safe to ignore.
create_date	The time the hazard object was created. The value is a Unix timestamp.
description	A human-readable description of the hazard.
end_Date	The time the hazard will expire if it is set to auto-expire. The value is a Unix timestamp.
glide_Uri	Deprecated. Safe to ignore.
hazard_ID	The primary key for this hazard.
hazard_Name	The human-readable name for this hazard.
in_Dashboard	Safe to ignore.
last_Update	The time that the hazard was last updated. The value is a Unix timestamp.
latitude	The hazard’s latitude in WGS84 projection.
longitude	The hazard’s longitude in WGS84 projection.
master_Incident_ID	Safe to ignore.
message_ID	Safe to ignore.
org_ID	The organization that owns this hazard. Safe to ignore unless you are creating or updating products.
product_total	The number of products associated with this hazard.
severity_ID	The severity of this hazard e.g. WATCH, WARNING
snc_url	An optional URL that links to a web page that contains a human-readable summary of the hazard.
start_Date	The time this hazard was started. The value is a Unix timestamp.
status	Indicates the current status of this hazard. There are two possible values: A (Active) or E (Expired)
type_ID	The type for this hazard e.g. AVALANCHE, CYCLONE.
update_Date	The time the hazard object was last modified.
update_User	If this hazard was modified by a user, the value will be the user’s username.
uuid	The unique identifier for this hazard across all DisasterAWARE systems.