> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/api/api.ews.03-fetch-alert.md). # API.EWS.03 Fetch Alert #### OGC API Features Adoption To ensure interoperability with existing geospatial systems and standards, DCI EWS standard adopts the **OGC API Features** standard as the primary mechanism for querying early warning alerts. Within this specification, **alerts are represented as an OGC API Features collection**. Implementations expose an **`alerts`** collection (for example, `GET /collections/alerts`) where each feature corresponds to a single alert. The feature geometry represents the spatial extent of the alert, while the feature properties contain the complete **CAP Alert** object, preserving all alert information defined by the Common Alerting Protocol (CAP). This approach enables clients to leverage the standard OGC API Features capabilities for discovery, retrieval, and filtering without introducing custom API patterns. Consumers can retrieve all alerts from the collection or query specific alerts using standard OGC API Features query parameters. Filtering is performed against the feature **properties**, which contain the embedded CAP Alert object. This allows clients to search alerts using CAP attributes such as: * Alert identifier * Sender * Status * Message type * Scope * Event type * Severity * Urgency * Certainty * Effective and expiry times * Any other standardized CAP field exposed within the feature properties By adopting OGC API Features, the specification remains fully compatible with the broader OGC ecosystem while preserving the complete CAP information model, enabling both geospatial and semantic queries through a standardized, interoperable API. ### Some usage Examples ``` Retrieve flood alerts: GET /collections/alerts/items?event=Flood Retrieve alerts with extreme severity: GET /collections/alerts/items?severity=Extreme Retrieve alerts requiring immediate action: GET /collections/alerts/items?urgency=Immediate ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/api/api.ews.03-fetch-alert.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.