> 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.04-create-replace.md).

# API.EWS.04 Create-replace

In addition to supporting the discovery and retrieval of alerts, DCI EWS standard adopts the OGC API Features approach for managing alert resources through standard HTTP operations.

Each alert is represented as an individual feature within the `alerts` collection. Early warning systems may create, update, or remove alert features using standard RESTful operations defined by OGC API Features.

* **Create** – A new alert is published by creating a new feature in the `alerts` collection. The feature contains the alert geometry and the complete CAP Alert object within its properties.
* **Replace** – When an alert is revised, the existing feature is replaced with an updated representation. The replacement includes the complete updated CAP Alert object, ensuring the feature remains a complete representation of the current alert state.

**Example Operations**

Create a new alert:

```
POST /collections/alerts/items
```

Replace an existing alert:

```
PUT /collections/alerts/items/{alertId}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/api/api.ews.04-create-replace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.