> For the complete documentation index, see [llms.txt](https://api-v2-docs.disasteraware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-v2-docs.disasteraware.com/hazards/requesting-a-hazard.md).

# Requesting a Hazard

To request a single hazard by its identifier, use the route defined here:

{% openapi src="/files/wYQaKpPZEdPb68ZWOF6w" path="/hazards/{hazard-id}" method="get" %}
[openapi.yaml](https://3664004773-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbwQ2AvqpbIy1hD3QFTQG%2Fuploads%2Fgit-blob-6ce5cdcf68a669c43075c73e6fae4e43d743a2d7%2Fopenapi.yaml?alt=media)
{% endopenapi %}

{% hint style="info" %}
See [Authorizing Requests](/authentication/authorizing-requests.md#get-accesstoken-and-refreshtoken) page to get your accessToken.
{% endhint %}

## Identifying the hazard

Every V2 hazard payload carries a `uuid`. Pass that value in the path to get the **complete V2 hazard record** back — the same shape as the [hazard sample pages](/hazards/hazard-samples/earthquake-sample.md), with `alertGeometry`, `features`, `exposureAreas`, and `exposureAssessment` inline. This works whether the hazard is currently active or has already moved to the historical archive, so a `uuid` you captured from `/active-hazards-query` remains resolvable after the hazard expires.

```
GET /hazards/c554507b-c769-43ab-8c67-07c116d4aa8c
```

Records served from the historical archive additionally carry three fields that active records do not: `legacy_hazard_id` (the hazard's V1 numeric id), `location` (a reverse-geocoded administrative block), and any enhancement blocks such as `earthquakeAssessment` or `cycloneAssessment`. These are described in [Requesting Historical Hazards](/hazards/requesting-historical-hazards.md#the-full-record).

### Legacy numeric ids

A **numeric** value in the same path position is treated as a legacy V1 `hazard_ID`:

```
GET /hazards/471892
```

This is a compatibility passthrough for clients that have not migrated to `uuid`. It returns the **V1-shaped** record — snake\_Case keys such as `hazard_ID`, `type_ID`, and `create_Date`, with epoch-millisecond string timestamps — wrapped in a one-element array. It does not include the V2 `incident`, `alertGeometry`, `features`, or exposure blocks.

{% hint style="warning" %}
The numeric form is a legacy construct. New integrations should use `uuid`, which returns the full V2 record. The V1 `hazard_ID` of a historical hazard is available as `legacy_hazard_id` on its V2 record, so you can map existing ids forward.
{% endhint %}

## Responses

| Status  | Meaning                                                                                                                                                         |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **200** | The hazard. A single V2 object for a `uuid`; a one-element array of the V1 record for a numeric id.                                                             |
| **400** | The path value is neither a uuid nor a number. Body: `{"error": "Invalid hazard identifier", "message": "Expected a V2 uuid (or a legacy numeric hazard_ID)."}` |
| **404** | No active or historical hazard has that uuid. Body: `{"error": "Hazard not found", "message": "No active or historical hazard with uuid <uuid>."}`              |
| **403** | Invalid or expired token.                                                                                                                                       |

## Example

```bash
curl -s -H "Authorization: Bearer $TOKEN" \
  'https://api-v2.disasteraware.com/hazards/c554507b-c769-43ab-8c67-07c116d4aa8c' | jq '{uuid, type, severity, legacy_hazard_id, location}'
```

```json
{
  "uuid": "c554507b-c769-43ab-8c67-07c116d4aa8c",
  "type": "EARTHQUAKE",
  "severity": "ADVISORY",
  "legacy_hazard_id": 471892,
  "location": {
    "admin0": "United States of America",
    "admin0_iso2": "US",
    "admin0_iso3": "USA",
    "admin1": "Alaska",
    "admin1_code": "US-AK",
    "admin2": "Denali",
    "admin2_code": "02068",
    "continent": "North America",
    "subregion": "Northern America",
    "location_type": "land",
    "source": "arcgis_reverse_geocoder"
  }
}
```

Unlike the query endpoints, this endpoint returns the record inline as JSON — there is no redirect and no compression.