# Introduction Documentation for DisasterAWARE Enterprise V2 API This documentation outlines the specifications for the DisasterAWARE Enterprise V2 API. Please note that the response structure of certain endpoints is subject to potential modifications in the future as we refine and enhance functionality to better meet user needs. Users are encouraged to review this documentation periodically to stay informed of any updates. ### Active Hazards Endpoint Limitations The V2 API is based on, and delivering hazards reported by the new hazard identification system, known as **RICHTER**. Hazards delivered via the V1 API, lack several fields such as `incident`, `alertGeometry`, `features`, and `exposureAssessment` which required additional API calls, or were not available at all. The V2 API was explicitly designed to reduce the number of API calls required to pull all hazard information. The V2 API is nearing completion, with only a few hazards remaining to be implemented. You are more than welcome to use the V2 API for prototypes and proof of concepts, but do not deploy in production until we declare this API is complete. As we complete the development, we might make additional changes to the structure of the data to make is more usable, and remove an extraneous information not relevant. Please contact if you have any questions regarding our API's. ### OpenAPI Specification {% file src="" %} Download OpenAPI Specification {% endfile %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://api-v2-docs.disasteraware.com/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.