Skip to content
Genesis Ark

Developers

Three standard interfaces, one order model

Qubit speaks the protocols your systems already use. FIX 4.4 for order flow from OMSs and trading desks, REST for order entry and reference data, and WebSocket for streaming execution reports, positions and market data. All three share one order model and one set of identifiers, so an order entered over FIX can be followed over WebSocket and queried over REST.

The samples below show the shape of the APIs. Paths, field names and tags are confirmed in the API reference shipped with each release, which you receive with sandbox access.

A FIX session: logon, a NewOrderSingle and the execution reports that follow it. Illustrative composition with sample data.

FIX 4.4

For order entry, drop copies and execution reports between institutional systems.

  • Order entry: NewOrderSingle (D), OrderCancelRequest (F), OrderCancelReplaceRequest (G), OrderStatusRequest (H)
  • Execution reports (8) for every state change, including partial fills, with cumulative and average fill fields
  • Drop copy sessions for compliance and back-office systems
  • Session-level sequence number recovery and resend handling, per the FIX standard
  • A rules of engagement document for each client describing supported tags, values and any custom fields
  • Sessions over TLS, or over a private network link in self-hosted deployments

Sample: NewOrderSingle for a limit buy of 2.5 BTC/USDT, sent to the smart order router

The | character stands in for the SOH field delimiter. Fields are shown one per line for reading.

FIX 4.4 · NewOrderSingle (35=D)
8=FIX.4.4|9=172|35=D|34=215|49=ACME_OMS|52=20261031-09:30:15.123|56=QUBIT|1=FUND-A|11=ACME-20261031-0001|21=1|38=2.5|40=2|44=64250.00|54=1|55=BTC/USDT|59=1|60=20261031-09:30:15.120|100=SOR|10=190|
Tags used in the NewOrderSingle sample
TagFieldValue in this sample
35MsgTypeD (NewOrderSingle)
1AccountFUND-A, the Qubit account the order books to
11ClOrdIDYour unique order ID. Resending the same ClOrdID never creates a second order.
21HandlInst1, automated execution
38OrderQty2.5
40OrdType2, limit
44Price64250.00, an illustrative price
54Side1, buy
55SymbolBTC/USDT in Qubit's normalized symbology
59TimeInForce1, good till cancel
100ExDestinationSOR routes through the smart order router. A venue code routes directly to that venue.

Change policy

Versioning and change policy

  • REST and WebSocket APIs carry a major version in the path (/api/v1, /ws/v1).
  • Within a major version, changes are additive: new endpoints, new optional fields, new enum values. Write clients that ignore fields they do not recognize.
  • Breaking changes ship only in a new major version. The previous version keeps working through a deprecation period stated in the release notes.
  • FIX changes are recorded in your rules of engagement document and announced before the release that carries them.
  • Every release lists API changes in its release notes.

Sandbox

Sandbox access

A sandbox with simulated venues and sample instruments is available on request, together with the full API reference, the FIX rules of engagement and test credentials. Ask for access through Contact and tell us which interfaces you plan to use.

SDKs

Roadmap

Typed client libraries for TypeScript and Python are on the roadmap. Until they ship, the API reference includes an OpenAPI description for REST, which you can use to generate a client in your language.

Request sandbox access

Tell us which interfaces you will use and what you want to test. We will send credentials, the API reference and the FIX rules of engagement.