---
title: "Acknowledge a drift alert"
method: POST
path: "/orgs/{org_id}/drift/{alert_id}/acknowledge"
tags: ["Drift"]
---

# Acknowledge a drift alert

`POST /orgs/{org_id}/drift/{alert_id}/acknowledge`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/orgs/{org_id}/drift/{alert_id}/acknowledge`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Marks a drift alert as acknowledged. Governance-scoped mutation: only org owner / admin may acknowledge (member, viewer and auditor cannot). Unknown `alert_id` returns 404. Emits a `drift.resolved` webhook (fail-open). Feature-gated: `fleet_dashboard`.

## Path parameters

- `org_id` string, required
- `alert_id` string, required

## Response `200`

Acknowledged.

- object
  - `acknowledged` boolean
  - `alert_id` string
  - `acknowledged_by` string
  - `acknowledged_at` string, date-time

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `402`: Paid feature gate — the caller's plan doesn't include this operation's feature flag. Emitted by `requireFeature` / `requireEntitlement` in `src/org/rbac.ts`.
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)