# WatchTower API Fields - DEPRECATED

<mark style="color:red;">**THIS ENDPOINT HAS BEEN DEPRECATED AND WILL NO LONGER BE ACTIVELY MAINTAINED OR UPDATED**</mark>

The following alerting fields are currently provided via the Network Alerts API endpoint:

```
{
  "data" : [ {
    "asset" : "the ticker of the asset monitored",
    "time" : "the time the alert was issued",
    "alert" : "the Alert ID",
    "block_height": "Optional: Returns the block height at which the alert tirggered, if the alert is calculated on a block by block basis. Otherwise this field is omitted from the response.",
    "status" : "whether the alerting condition is still in place (active), or no longer observed (inactive)",
    "value" : "the value of the alerting metric",
    "threshold" : "the alerting threshold for the metric"
  } ]
  "heartbeats": [
    {
      "asset": "the ticker of the asset monitored",
      "time": "the last time the corresponding alert was calculated",
      "alert": "the Alert ID"
    } ]
}
```

For all alerts, heartbeats are calculated each time the underlying data is updated. In most cases this is each time a new block is generated. However, for some alerts this might be on a different frequency as well. For example, for the BTC alert `mining_pool_conflict_2b_hi` the alert is calculated every time there is an update in the [mining-pool-tips-summary](https://gitlab.com/coinmetrics/front-end/knowledge-base/-/blob/master/docs/watchtower-alerts-time-series-deprecated/watchtower-alerts-overview-deprecated/broken-reference/README.md) endpoint.


---

# 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://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-api-fields-deprecated.md?ask=<question>
```

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.