Requesting Historical Hazards

The endpoint for fetching historical hazards:

Search historical hazard records

get

Query the historical hazard database using a SQL-style where clause. Returns an array of matching hazard records.

Authorizations

bearerAuth

AuthorizationstringRequired

JWT access token obtained from POST /authorize. Tokens expire after 15 minutes.

Query parameters

wherestringRequired

SQL-style filter expression. Example: type_ID='EARTHQUAKE' AND severity_ID='WARNING'

Example: type_ID='EARTHQUAKE'

Responses

200

Array of matching historical hazard records.

application/json

A historical hazard record.

app_IDintegerOptional

Application ID.

Example: 1

app_IDsstringOptional

Comma-separated application IDs.

autoexpirestringOptional

Auto-expiration flag.

category_IDstringOptional

Category identifier.

Example: NATURAL

charter_UristringOptional

International Charter URI, if applicable.

comment_TextstringOptional

Editorial comment.

create_DatestringOptional

Creation timestamp in epoch milliseconds.

Example: 1697157024387

creatorstringOptional

Record creator.

Example: DisasterAWARE (Automated)

end_DatestringOptional

End timestamp in epoch milliseconds.

glide_UristringOptional

GLIDE number URI.

hazard_IDintegerOptional

Numeric hazard identifier.

Example: 203575

hazard_NamestringOptional

Human-readable hazard name.

Example: M 5.2 Earthquake - Southern Peru

last_UpdatestringOptional

Last update timestamp in epoch milliseconds.

latitudenumberOptional

Latitude of the hazard centroid.

Example: -16.25

longitudenumberOptional

Longitude of the hazard centroid.

Example: -71.58

master_Incident_IDstringOptional

Master incident identifier.

message_IDstringOptional

Associated message identifier.

org_IDintegerOptional

Organisation ID.

severity_IDstringOptional

Severity identifier.

Example: WARNING

snc_urlstringOptional

Situational awareness URL.

start_DatestringOptional

Start timestamp in epoch milliseconds.

Example: 1697157024387

statusstringOptional

Hazard status (e.g. active, expired).

type_IDstringOptional

Hazard type identifier.

Example: EARTHQUAKE

update_DatestringOptional

Update timestamp in epoch milliseconds.

update_UserstringOptional

User who last updated the record.

product_totalstringOptional

Total number of associated products.

uuidstringOptional

Unique identifier.

in_DashboardstringOptional

Whether the hazard appears in the dashboard.

areabrief_urlstring · nullableOptional

URL to the area brief, if available.

descriptionstringOptional

Hazard description text.

rolesstring[]Optional

Roles associated with the hazard.

403

Forbidden -- invalid or expired token.

text/plain

get

/historical_hazards

HTTPcURLJavaScriptPython

GET /historical_hazards?where=text HTTP/1.1
Host: api-v2.disasteraware.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

[
  {
    "app_ID": 1,
    "app_IDs": "text",
    "autoexpire": "text",
    "category_ID": "NATURAL",
    "charter_Uri": "text",
    "comment_Text": "text",
    "create_Date": "1697157024387",
    "creator": "DisasterAWARE (Automated)",
    "end_Date": "text",
    "glide_Uri": "text",
    "hazard_ID": 203575,
    "hazard_Name": "M 5.2 Earthquake - Southern Peru",
    "last_Update": "text",
    "latitude": -16.25,
    "longitude": -71.58,
    "master_Incident_ID": "text",
    "message_ID": "text",
    "org_ID": 1,
    "severity_ID": "WARNING",
    "snc_url": "text",
    "start_Date": "1697157024387",
    "status": "text",
    "type_ID": "EARTHQUAKE",
    "update_Date": "text",
    "update_User": "text",
    "product_total": "text",
    "uuid": "text",
    "in_Dashboard": "text",
    "areabrief_url": "text",
    "description": "text",
    "roles": [
      "text"
    ]
  }
]

See Authorizing Requests page to get your accessToken.

Checking Result Count

Before querying historical hazards, use the hazards_count endpoint to verify your search will return fewer than 1000 matches:

https://api-v2.disasteraware.com/hazards_count?where=<your_query>

Query Fields

The where parameter accepts the following fields:

Field	Description	Example
status	Hazard status. Use 'E' for expired hazards.	status = 'E'
type_id	Hazard type: AVALANCHE, TORNADO, WILDFIRE, etc.	type_id = 'AVALANCHE' OR type_id = 'WILDFIRE'
category_id	Hazard category: EVENT, EXERCISE, OTHER, RESPONSE	category_id = 'EVENT'
severity_id	Hazard severity: WARNING, WATCH, ADVISORY, INFORMATION	severity_id = 'WARNING'
hazard_name	Hazard name (use UPPER() and LIKE for case-insensitive search)	UPPER(hazard_name) LIKE '%HAWAII%'
comment_text	Any comment text associated with the hazard	UPPER(comment_text) LIKE '%TSUNAMI%'
create_date	Hazard creation date, typically used to check a range of dates	create_date >= to_date('2023-05-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND create_date <= to_date('2023-05-31 00:00:00', 'yyyy-mm-dd hh24:mi:ss')
latitude / longitude	Bounding box using latitude and longitude	(latitude >= 36.58 AND latitude <= 39.06) AND (longitude >= -123.99 AND longitude <= -119.68)

Examples

Filter by hazard type

?where=type_id = 'WILDFIRE'

Filter by multiple types

?where=type_id = 'AVALANCHE' OR type_id = 'WILDFIRE'

Search by hazard name (case-insensitive)

?where=UPPER(hazard_name) LIKE '%HAWAII%'

Filter by date range

?where=create_date >= to_date('2023-05-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND create_date <= to_date('2023-05-31 00:00:00', 'yyyy-mm-dd hh24:mi:ss')

Filter by geographic bounding box

?where=(latitude >= 36.58151 AND latitude <= 39.06433) AND (longitude >= -123.99719 AND longitude <= -119.68719)

Multi-field query

The following searches for expired WILDFIRE hazards of type EVENT, severity WARNING, created between 5/1/23 and 5/31/23, with "namefoo" (case-insensitive) in the hazard name and "commentfoo" (case-insensitive) in the comment text:

https://api-v2.disasteraware.com/hazards_count?where=((category_id = 'EVENT')) AND (UPPER(comment_text) LIKE '%COMMENTFOO%') AND (create_date >= to_date('2023-05-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss') AND create_date <= to_date('2023-05-31 00:00:00', 'yyyy-mm-dd hh24:mi:ss')) AND (UPPER(hazard_name) LIKE '%NAMEFOO%') AND ((severity_id = 'WARNING')) AND ((status = 'E')) AND ((type_id = 'WILDFIRE'))

The multi-field example above uses the hazards_count endpoint to first verify the result count before fetching the actual hazards via historical_hazards.