Skip to main content
POST
/
v1
/
anomalies
/
{anomalyId}
/
resolve
Resolve Anomaly
curl --request POST \
  --url https://api.truthlocks.com/v1/anomalies/{anomalyId}/resolve \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "resolution": "<string>",
  "resolved_by": "<string>"
}
'
{
  "anomaly_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "agent_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "anomaly_type": "<string>",
  "severity": "low",
  "details": {},
  "status": "open",
  "resolution": "<string>",
  "resolved_by": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "resolved_at": "2023-11-07T05:31:56Z"
}
Resolves an open behavioral anomaly. The resolution records the investigator’s determination — whether the anomaly was a false positive, was mitigated, represents an accepted risk, or resulted in the agent being revoked. Resolution events are immutable once recorded. If an anomaly’s resolution needs to be revisited, a new anomaly should be created referencing the original.

​
Resolution Types

ResolutionDescriptionEffect
false_positiveAnomaly was not a genuine threatAuto-response reversed (agent restored)
mitigatedAnomaly was genuine and has been addressedAuto-response remains; agent may be restored manually
accepted_riskAnomaly is genuine but accepted per policyAuto-response reversed; risk documented
agent_revokedAnomaly led to permanent agent revocationAgent remains revoked

​
Authentication

​
X-API-Key
string
required
API key with anomalies:resolve scope. Alternatively, pass a Bearer JWT token in the Authorization header.
​
X-Tenant-ID
string
required
Tenant identifier for multi-tenant isolation.

​
Path Parameters

​
id
string
required
Anomaly identifier (maip-anom:ULID). Must be in open status.

​
Request

​
resolution
string
required
Resolution determination. Must be one of: false_positive, mitigated, accepted_risk, agent_revoked.
​
notes
string
Investigator notes explaining the resolution decision. Stored in the audit trail.

​
Response

​
id
string
Anomaly identifier.
​
agent_id
string
The agent associated with the anomaly.
​
anomaly_type
string
Type of anomaly.
​
severity
string
Severity level.
​
status
string
Updated status: resolved.
​
resolution
string
Resolution determination.
​
notes
string
Investigator notes.
​
resolved_at
string
ISO 8601 timestamp of resolution.
​
resolved_by
string
Operator or API key identifier that resolved the anomaly.
​
created_at
string
ISO 8601 timestamp of original anomaly creation.

Authorizations

​
X-API-Key
string
header
required

API key for machine-to-machine authentication

Path Parameters

​
anomalyId
string<uuid>
required

Anomaly identifier

Body

application/json
​
resolution
string
required

Description of how the anomaly was resolved

​
resolved_by
string
required

Identifier of the resolver (agent or user)

Response

Anomaly resolved

​
anomaly_id
string<uuid>
​
agent_id
string<uuid>
​
anomaly_type
string
​
severity
enum<string>
Available options:
low,
medium,
high,
critical
​
details
object
​
status
enum<string>
Available options:
open,
investigating,
resolved,
dismissed
​
resolution
string
​
resolved_by
string
​
created_at
string<date-time>
​
resolved_at
string<date-time>