Execution services
How the product API, off-chain execution engine, live streams and Canton settlement work together.
Backend services
Backend services
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
The API connects clients to the execution core. Committed execution evidence feeds account and market streams, query views and settlement processing.
Execution. The native core orders eligible commands, applies risk and matching rules, and produces durable off-chain outcomes.
Delivery. WebSockets carry live updates. Query services provide snapshots and history with their own freshness and completeness.
Settlement. Eligible effects are submitted to Canton. Confirmed ledger facts feed settlement status and reconciliation.
From product API to execution
The product API authenticates a request, checks its permissions and validates its fields before sending an eligible command to the execution engine. Idempotency links retries to the same logical command. Bun/Hono services connect the public API to a native C++ financial core, which orders commands and applies matching and risk rules.
Execution commits off-chain. Settlement follows asynchronously on Canton, so order processing does not wait for a blockchain response. Read services, WebSockets and settlement each expose a different stage of the same financial lifecycle.
Execution, account state and history
Execution can commit before every historical query has caught up. A live position view and a historical position record may therefore have different freshness. Use the response’s available timestamps, sequence metadata and completeness indicators to understand the data you receive.
Build integrations against product-level APIs and streams. Keep accepted commands, current account state and confirmed settlement distinct in your interface. A successful history query does not prove that every live account view is current.
Choose the available integration
Edel Markets is on Devnet, with Testnet and Mainnet coming soon. Authentication methods, supported markets and integration capabilities depend on the target environment. Check availability before connecting an application or placing orders.
Trading applications use the product API and WebSockets. Agents can use MCP where enabled, under owner-approved permissions. Market makers use the same public REST and WebSocket interfaces with the required account permissions. See API capabilities, market-maker integration and the REST API reference and realtime API reference.