Three real ways in, one consistent experience
MatchCore speaks FIX, a dedicated low-latency binary protocol, and WebSocket/REST for browser clients — three genuinely separate integration paths that all route through the same order-management logic, so behavior never drifts between them.
FIX
Session handshake, order entry and cancel/replace, execution reports, and a real read-only DropCopy session type for compliance mirroring.
Low-Latency API
A dedicated binary protocol for professional clients — auth, order entry, push execution reports, and market data. Its reference documentation is generated automatically, so it never drifts from what's actually live.
WebSocket & REST
JSON order entry, account endpoints, and a streaming WebSocket feed for real-time market data — what our own browser frontend and desktop demo clients use.
Admin API
Market lifecycle, resolution, and house liquidity-seeding, gated separately from client order flow.
Built against these APIs, running today
Both a native C++ client and a Java desktop client exist and run against our low-latency API — live order depth, time & sales, and charting, not a mockup. If you're evaluating whether an API is real or aspirational, ask to see one of these connect to a live matching engine.
New order, over FIX
| 35=D | MsgType = NewOrderSingle |
| 55=MC.BIN.ELECTION-2028 | Symbol — binary market instrument |
| 40=2 | OrdType = Limit |
| 44=0.64 | Price |
| 38=1200 | OrderQty |
| 59=1 | TimeInForce = GTC |
From sandbox to production
| Environment | Purpose | Data |
|---|---|---|
| Sandbox | Integration testing against a standard instance | Synthetic |
| Staging | Pre-production validation on your chosen topology (standard or clustered) | Anonymised replay |
| Production | Live trading on your provisioned deployment | Live |