Enterprise API & integrations

Bring forensic intelligence into your operating environment.

Submit cases, retrieve authorised findings, access published reports and run targeted wallet checks through a governed API—then scope deeper workflow integration around the way your team already works.

Discuss integration →View interface ↓

Organisation-issued keysPermission scopesUsage controls

Integration flowv1

POST /api/v1/cases

{ "blockchain": "ethereum",
  "loss_txid": "0x...",
  "incident_type": "investment_fraud",
  "tier": "tier2" }

201 CREATED{ "case_ref": "CT-...", "status": "submitted" }

Intake→Review→Findings→Report

X-API-Key authenticationRead / Submit / Trace permissionsPer-key rate limitsRequest usage visibility

Where it fits

Connect the hand-offs that slow investigations down.

Use the API as a controlled bridge between your intake, matter management, investigation and reporting processes.

↳

Submit without re-keying

Send structured incident information from an existing intake, CRM or case-management flow into Chain Trace Labs.

◎

Bring status into view

Let authorised users see case state, risk context and published findings in the systems they already monitor.

⌁

Check a wallet on demand

Request a targeted supported-chain wallet check with known entity, risk and sanctions context where available.

↓

Retrieve approved outputs

Download a forensic report only after it has completed review and been published for the authorised account.

Current core interface

Six endpoints. Clear operational purpose.

This reflects the implemented v1 gateway. Detailed schemas, credentials and environment documentation are provided during onboarding.

MethodResourceWhat it enablesScope

GET/casesList cases available to the authenticated accountread

GET/cases/{ref}Retrieve case state and authorised published findingsread

GET/cases/{ref}/reportDownload the reviewed report after publicationread

POST/casesCreate a structured investigation requestsubmit

POST/traceRun an ad-hoc wallet and entity context checktrace

GET/usageView key permissions, limits, totals and expirykey

What remains private

Internal analytical controls, restricted case material, analyst notes, unpublished findings and security configuration are not exposed through the public interface.

Beyond the core API

Integration can follow the full case lifecycle.

The portal contains a broader operating layer. Where the use case, permissions and governance support it, implementation can be scoped around selected workflow events and approved outputs.

Core API todayScoped integration

Your systemsChain Trace Labs integration layerGoverned access

Case intakeCreate and retrieve matters

Workflow operationsStages, tasks and ownership

Evidence & legalApproved records and outputs

MonitoringWallet and case signals

OSINT & correlationReviewed intelligence context

Reports & findingsPublished delivery

Available platform depth

Scope around the outcome, not just the endpoint.

These platform capabilities can inform an enterprise implementation without implying that every function is an unrestricted public API.

INVESTIGATE

Forensic intelligence

Multi-chain tracing, AML/KYT context, entity interactions, fraud patterns and reviewed narrative outputs.

Trace intelligenceWallet contextRisk indicators

ENRICH

OSINT and communications

Domain, identity, communication and external intelligence signals connected to the authorised case record.

OSINT reviewChat analysisAttribution cues

OPERATE

Case workflow

Intake, triage, assignments, team tasks, deadlines, client updates and controlled case-stage visibility.

TasksStagesRoles

PRESERVE

Evidence and reporting

Evidence Vault records, custody context, professional reports, schedules and authorised case-pack delivery.

EvidenceReportsAudit context

ACT

Legal and escalation

Exchange contacts, freeze-request tracking, LE referral, legal documents and recovery-action coordination.

Freeze workflowLE routingLegal packs

WATCH

Monitoring and correlation

Wallet movement, alert workflows, linked cases and recurring entity or infrastructure signals.

WatchlistsAlertsCase links

Controlled access

Designed for accountable use.

Hashed credentials

Issued API keys are stored and checked by hash; keys can be expired or revoked.

Scoped permissions

Read, submission and trace privileges can be assigned independently.

Account boundaries

Case queries are restricted to the authenticated account’s records.

Publication control

Report findings and downloads remain unavailable until authorised publication.

Rate governance

Per-key request limits help keep access predictable and manageable.

Usage records

Request totals, recent use and key metadata support operational oversight.

Implementation path

From proof of fit to controlled rollout.

1DiscoverySystems, users, volumes and outcomes

2ScopeData contract, permissions and boundaries

3ValidateTest environment and representative cases

4LaunchCredentials, controls and supported rollout

Build the right connection

Let’s map your investigation workflow.

Tell us what enters your systems, what your teams need to receive and where decisions currently slow down.

Discuss enterprise integration →