---
title: "Resolve a detected campaign"
method: POST
path: "/safe-house/campaigns/{campaign_id}/resolve"
tags: ["Safe House"]
---

# Resolve a detected campaign

`POST /safe-house/campaigns/{campaign_id}/resolve`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/safe-house/campaigns/{campaign_id}/resolve`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Authorization: the caller must be authenticated, resolve to an organization and hold the owner, admin or member role in it (viewers and auditors are read-only and get 403), and `campaign_id` is matched scoped to that organization (`org_id`), so a campaign owned by another tenant returns 404 and no other tenant's campaign can be resolved.

## Path parameters

- `campaign_id` string, required

## Request body

- object
  - `resolution` string
  - `notes` string

## Response `200`

Resolved.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `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.

---

[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)