---
title: "Add a new threat pattern"
method: POST
path: "/safe-house/patterns"
tags: ["Safe House"]
---

# Add a new threat pattern

`POST /safe-house/patterns`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/safe-house/patterns`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Requires API key or bearer JWT, and the owner, admin or member role in the caller's organization (viewers and auditors are read-only and get 403). `label: "benign"` adds a known-safe pattern (reduces false positives).

## Request body

- object
  - `threat_type` string, required
  - `content` string, required
  - `label` 'malicious' | 'benign', required
  - `source` string
  - `minhash` string, nullable
  - `metadata` object

## Response `201`

Pattern created.

- SafeHousePattern: Row from `sh_threat_patterns`. `label: "benign"` patterns are used to suppress false positives; `label: "malicious"` patterns add to L1/L2 detection.
  - `id` string
  - `threat_type` string
  - `source` string
  - `label` 'malicious' | 'benign'
  - `content` string
  - `minhash` string, nullable
  - `metadata` object
  - `is_active` boolean
  - `created_at` string, date-time

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