API Reference

Loci APIs are organized by operational domain. Most clients start with transaction monitoring, then add rules, testing, alerts, cases, entity intelligence, and optional modules as their rollout expands.

Core APIs

• Transaction Monitoring API Reference: score transactions, inspect transactions, query graph context, and manage transaction-level outcomes.
• Rules API: list, create, update, deploy, pause, and inspect rule definitions.
• Rule Testing API: test inactive rules against manual payloads or historical transactions.
• Alerts API: claim, assign, release, resolve, and inspect alert queues.
• Cases API: create cases, link alerts, record notes, update status, submit dispositions, and handle approvals.
• Entity Intelligence API: retrieve graph, centrality, beneficiary, and entity relationship context. See also Entity Centrality And Network Intelligence.

Optional Module APIs

• AccessGate API: device and session risk checkpoints.
• AccessGate AML API: sanctions, PEP, watchlist, whitelist, feedback, and relationship screening.

Integration Pattern

Server-side systems call Loci with tenant-scoped credentials. Real-time decision paths should stay lightweight. Heavy exports, historical analysis, and reporting should run through asynchronous jobs or analytical stores so online evaluation remains reliable.

Canonical Transaction Reference

The transaction monitoring reference is generated from the current public Postman collection and is available at Transaction Monitoring API Reference.