---
title: "Withdraw an acknowledgement"
url: https://docs.corefinity.com/api/reference/sites/unacknowledge-attention
type: endpoint
last_updated: 2026-11-13
feature: sites
related:
  - https://docs.corefinity.com/guides/sites/create-and-manage/site-overview.md
  - https://docs.corefinity.com/mcp/tools/corestack_attention_unack.md
---
# Withdraw an acknowledgement

Withdraws the acknowledgement of an item, so it counts as needing attention again.

```http
DELETE /api/corestack/attention/{attention}/ack
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 60 a minute
- Try it in the console: on

## Path parameters

- `attention` (string, required): The `id` of an item of the attention list, URL-encoded: a kind, a colon, a number and sometimes a further part, such as `site_down:1051` (sent as `site_down%3A1051`).

## Request

### curl

```bash
curl -X DELETE https://manage.corefinity.com/api/corestack/attention/site_down%3A1051/ack \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json"
```

### PHP

```php
use Illuminate\Support\Facades\Http;

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->delete('https://manage.corefinity.com/api/corestack/attention/site_down%3A1051/ack');

$data = $response->json();
```

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/corestack/attention/site_down%3A1051/ack', {
  method: 'DELETE',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
  },
});

// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);
```

### Python

```python
import os
import requests

res = requests.delete(
    "https://manage.corefinity.com/api/corestack/attention/site_down%3A1051/ack",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
)

data = res.json() if res.content else None
```

## Responses

### 200 The parts of the overview the withdrawal changed.

```json
{
  "overview_patch": {
    "attention": [
      {
        "acknowledgeable": true,
        "acknowledged": null,
        "action": null,
        "cluster": {
          "id": 1017,
          "name": "Northwind UK 1"
        },
        "detail": "No container is ready.",
        "environment": null,
        "href": "/managed-clusters/sites/1051",
        "id": "site_down:1051",
        "kind": "site_down",
        "scope": "site",
        "severity": "critical",
        "since": "2026-11-14T08:58:00Z",
        "site": {
          "domain": "journal.harbourandfinch.example.com",
          "id": 1051
        },
        "subject": null,
        "title": "Site is down"
      }
    ],
    "attention_acknowledged": [],
    "attention_acknowledged_total": 0,
    "attention_total": 1,
    "generated_at": "2026-11-14T09:02:00Z",
    "sites_attention": {
      "1051": 1
    }
  }
}
```

### 401 No token, or a token that is not valid.

```json
{
  "message": "Unauthenticated."
}
```

### 403 The token lacks the scope (`scope_required`, with the `scope` to use), your company requires two-factor authentication and you have not set it up, or your account has no company that can use Managed Clusters, for example because the company was closed (`company_unavailable` or `company_not_enabled`, whichever the route checks first). For Managed Clusters routes; any other route uses `ForbiddenScopeOrTwoFactor`.

```json
{
  "code": "company_unavailable",
  "message": "Your company is unavailable.",
  "reason": "company_unavailable"
}
```

### 404 The item has no acknowledgement to withdraw (`not_acknowledged`), attention acknowledgement is not on for your company (`feature_off`), or the id is not an item id.

```json
{
  "code": "feature_off",
  "message": "Not found.",
  "reason": "feature_off"
}
```

### 429 Too many requests (`rate_limited`). Wait for the number of seconds in `Retry-After`, which `retry_after_seconds` repeats.

```json
{
  "code": "rate_limited",
  "message": "Too many requests. Try again in 60 seconds.",
  "reason": "rate_limited",
  "retry_after_seconds": 60
}
```

## If it is refused

| Status | Reason | What to do |
|---|---|---|
| 401 |  | Send a valid token as `Authorization: Bearer <token>`. |
| 403 | `company_unavailable` | Your company is unavailable. |
| 403 | `scope_required` | Use a token with the scope named in `scope`. |
| 403 | `two_factor_required` | Turn on two-factor on your account, then send again. |
| 404 | `feature_off` | This feature is not on for your organisation yet. |
| 404 | `not_acknowledged` | The attention item has no acknowledgement to withdraw. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |

## The same task elsewhere

- Guide: [Site overview](https://docs.corefinity.com/guides/sites/create-and-manage/site-overview.md)
- MCP tool: [`corestack_attention_unack`](https://docs.corefinity.com/mcp/tools/corestack_attention_unack.md)
