Investigation case files
List investigation case files for a vessel — motif-anchored dossiers with evidence, auto-generated narratives, and analyst annotations from Overwatch.
Structured investigation dossiers built from temporal graph motifs and corroborating evidence.
Case files aggregate multiple signal types into a single narrative per vessel — dark events, spoofing alerts, STS transfers, destination deceptions, and more. Use them to build investigation workflows, export reports for regulatory handoff, or track case status across your team.
GET /api/v1/vessels/{imo}/case-files
503 feature_unavailable for every request — the investigation case files data model has not been deployed to this launch environment.Returns investigation case files for a vessel. Each case file is anchored to a temporal graph motif alert and includes all corroborating evidence, an auto-generated narrative, and analyst annotations.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
imo | string | ✓ | 7-digit IMO number (path param) |
cursor | number | Pagination offset (default 0) | |
limit | number | Results per page, 1–25 (default 10) |
Response
{
"error": "Investigation case files is not launch-supported",
"code": "feature_unavailable"
}This is the complete response body currently returned (HTTP 503) for every request, regardless of the parameters above — no case_files array is produced. The shape below reflects the intended design once the feature ships.
Errors
503(feature_unavailable) — Returned unconditionally: "Investigation case files is not launch-supported"
Evidence kinds
Each timeline entry has a kind field indicating the evidence type:
| Kind | Description |
|---|---|
dark_event | AIS gap or transmission loss |
spoofing | Kinematic or multi-source AIS anomaly |
sts_transfer | Ship-to-ship cargo transfer |
destination_deception | Declared destination does not match trajectory |
lifecycle_change | Flag, name, or MMSI change |
psc_inspection | Port state control detention or deficiency |
cargo_anomaly | Draft-based cargo estimation anomaly |
obfuscation_assessment | Deliberate identity or track obfuscation |
Example
curl -X GET -H "X-API-Key: YOUR_KEY" \
https://www.axiomoverwatch.io/api/v1/vessels/9876543/case-filesPATCH /api/v1/vessels/{imo}/case-files
503 feature_unavailable for every request — the investigation case files data model has not been deployed to this launch environment.Update annotations on a case file. Use this to change case status, add analyst notes, or set custom export fields for PDF generation and regulatory handoff.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
imo | string | ✓ | 7-digit IMO number (path param) |
case_id | string | ✓ | Case file identifier |
motif_alert_id | string | ✓ | Associated motif alert identifier |
status | string | 'open', 'reviewing', 'escalated', 'reported', or 'closed' | |
summary | string | Analyst-provided summary | |
notes | string | Free-form investigation notes | |
export_title | string | Custom title for PDF export | |
export_summary | string | Custom summary for PDF export | |
handoff_context | string | Context for handoff to another analyst or agency |
Response
{
"error": "Investigation case files is not launch-supported",
"code": "feature_unavailable"
}This is the complete response body currently returned (HTTP 503) for every request, regardless of the parameters above. The shape below reflects the intended design once the feature ships.
Errors
503(feature_unavailable) — Returned unconditionally: "Investigation case files is not launch-supported"
Example
curl -X PATCH -H "X-API-Key: YOUR_KEY" \
https://www.axiomoverwatch.io/api/v1/vessels/9876543/case-files \
-d '{"case_id":"CASE-ABCD-123456789012","motif_alert_id":"alert-xyz","status":"escalated","handoff_context":"Referred to compliance team"}'Signal intelligence
Fetch explainability breakdowns for spoofing, cargo, and motif signals on a vessel with score components, evidence timelines, and analyst feedback.
Investigations
Investigation case files, signal feedback, and explainability endpoints for vessel risk intelligence — close the loop between analysts and risk models.