Market data
GatewayIngestion (REST/WebSocket), snapshots, reference data, normalization.
Public PreviewTesting header enabled
Open sitemap
/integrations
Integrations
An integration model designed for institutional change.
Keep the domain core stable while vendors evolve. Integrations live behind ports, are auditable, and support both synchronous workflows and async processing.
What we integrate with
Operfix is built to connect to the ecosystem around portfolio, trading, and reporting—without leaking vendor complexity into core workflow.
Brokers / OMS
TradingOrder routing, acknowledgements, execution updates, cancellations.
Custodians
Post-tradeSettlement status, confirmations, reconciliations, exceptions.
Pricing / reference
DataInstrument metadata, curves, corporate actions feeds.
Climate / ESG
SpecialtyVendor overlays, emissions factors, scenario outputs.
Identity (SSO)
TrustOIDC/SAML, SCIM provisioning, enterprise policy hooks.
Reliability posture
Integrations are where operational risk concentrates. We design for traceability, idempotency, and controlled failure modes.
Contract boundary
Ports
Domain stays vendor-agnostic
Execution model
Sync + async
Workflows + job queues
Failure handling
Visible states
No silent drops
Traceability
Audit-by-default
Event IDs and correlation
How it works (high level)
A consistent pattern across modules: API action → use case → port → adapter → vendor.
1) Orchestrate
API/BFF01Route handlers accept a request, validate it, and call an application use case—no vendor code in the HTTP layer.
2) Enforce workflow
Application + domain02The use case applies policy, lifecycle transitions, and emits domain events for audit and async work.
3) Adapt
Infrastructure adapters03Adapters implement ports, translate formats, apply retries/backoff, and attach correlation IDs.
Integration patterns by workload
Choose the integration shape based on the risk and latency requirements.
| Capability | Use for | Guarantees | Operational notes |
|---|---|---|---|
| Synchronous (request/response) | Approvals, compliance checks, order actions | Immediate feedback, consistent user experience | Timeout budgets, clear error mapping, no long-running tasks |
| Asynchronous (jobs/events) | Market ingestion, risk runs, report generation | Retries, dedupe, backpressure | Queue visibility, dead-letter handling, measurable SLAs |
| Hybrid (sync trigger + async completion) | Trade confirmation, settlement updates, vendor reconciliation | User gets a tracking ID, status updates later | Status pages, audit trail, operator runbooks |
Integrations should not leak into the domain core.
Ports keep workflow stable; adapters evolve per vendor. Every vendor call is traceable, retryable where safe, and reflected in lifecycle state.
Related pages
Cross-links across the public site for architecture, trust, specialty modules, and rollout.
API Design
Versioned contracts and workflow-oriented endpoints.
Modules
Bounded contexts for core and expansion capabilities.
Workers
Async processing model for heavy workloads and reliability.
Observability
Structured logs, trace context, and queue visibility.
Contact
Commercial, technical, and governance inquiry channels.
Reliability
Exception-first handling for non-happy paths.