Skip to content
Order Management System APIs

Order Management System Concepts

The Order Management System is an timeseries database based around realtime tracking of Balances, Holdings, Orders, and associated information.

Architecture

Section titled “Architecture”

The OMS works by recording all incoming updates, and applying them in sequence to generate an up-to-date vision of the system. The update history can be retrieved using the Audit API.

OMS presents various views of the system, generating potentially multiple events from each update. The event history can be retrieved using the Event API or Event Audit API. This event-based system also allows for viewing the OMS state at any point in time.

Update Sources

Section titled “Update Sources”

All updates are supplied to OMS via the external API.

  • The WebSocket API is used to feed updates directly into OMS in realtime, and have their own independent tracking for reliability and recovery.
  • The REST API provides endpoints for submitting updates such as transactions and metadata with simple HTTP requests.

Monitoring

Section titled “Monitoring”

Multiple REST API endpoints are available for querying both the current and historical state, and for retrieving past events.

For applications attempting to maintain a realtime state, rather than polling these endpoints, the WebSocket API provides subscriptions with full state snapshots and streaming events.

Depending on the view being utilised, applications only need a minimal understanding of the business logic to maintain the state.

Metadata

Section titled “Metadata”

Beyond just tracking of Balances, Holdings, and Orders, OMS provides a multitude of trading-related metadata for downstream applications.

  • Trading Account metadata supply Account descriptions, vetting configuration, and more.
  • Exchange metadata describes the execution destinations and markets an application can expect to see.
    This is used by OMS to route Client Requests to the correct adapter for execution.
  • Feed metadata describes the status of any upstream OMS adapters, for system reporting.
  • Owner metadata describes Account owners, which can be thought of as tenants with their own Account code namesepaces.
  • Request Status describes the operations supported by the various stages an Order Request goes through in its lifecycle.

Except where noted, this metadata is not used by OMS directly, and is supplied by adapters for use by connected data systems.