12 / Connectivity
AvailableFIX, REST and WebSocket in, venue adapters out
Qubit's connectivity layer is how your clients, your systems and your venues reach the platform. Clients and internal systems connect over FIX, REST or WebSocket. Venues connect through adapters that handle each exchange's API, symbols, rate limits and reconnection rules.
- Layer
- Standalone · Add-on
- Works on its own
- Yes
- Interfaces
- FIX 4.4, REST, WebSocket
01 / The problem
Integration work should happen once
Every exchange integration has its own authentication, request signing, rate limits, error codes and quirks during maintenance windows. Every institutional client expects FIX and asks for a drop copy. Building and maintaining this for each venue and each client is where trading teams lose months. Qubit does it once, in a layer every module shares.
02 / What it does
What the layer provides
- 01
FIX for clients and systems
Order entry, drop copy and market data sessions, with per-session credentials, permissions and accounts.
- 02
REST API
Orders, positions, balances, reference data, configuration and reports, with consistent objects and errors.
- 03
WebSocket API
Streaming order updates, fills, positions, balances, prices and market data.
- 04
Venue adapters
One adapter per venue, translating Qubit's order and market data model into the venue's API and back.
- 05
Symbology mapping
One instrument ID for each tradable pair, mapped to each venue's symbol and rules.
- 06
Session resilience
Heartbeats, sequence number management, resend handling and automatic reconnection with state recovery.
- 07
Sandbox
A test environment where your developers and clients can certify against Qubit before connecting to production.
03 / How it works
How a connection is set up
- 01
Provision
An administrator creates a session or API credential, assigns it to accounts and sets its permissions: trade, view, or both.
- 02
Restrict
IP allowlists and, for FIX, session-level credentials and certificates are configured per connection.
- 03
Certify
The client or your developers test order flows in the sandbox against a documented test plan.
- 04
Go live
The connection is enabled for production with its limits and cancel-on-disconnect setting.
- 05
Monitor
Session state, message rates, rejects and disconnects are visible per connection in the console.
04 / Specifics
Technical specifics
- FIX
FIX 4.4. Session layer: Logon (35=A), Heartbeat (35=0), TestRequest (35=1), ResendRequest (35=2), Reject (35=3), SequenceReset (35=4), Logout (35=5). Application messages for orders, quotes and market data are listed on the Order management, RFQ and Market data pages.
- Drop copy
ExecutionReport (35=8) copies of every order event for an account or firm, to a separate session, for clients' risk and back-office systems.
- REST
JSON over HTTPS, versioned paths, idempotency keys on order creation, paginated queries, consistent error codes.
- WebSocket
Authenticated subscriptions per channel (orders, fills, positions, balances, prices, books), sequence numbers on every message and snapshot on resubscribe.
- Authentication
API keys with HMAC request signing or token-based authentication for REST and WebSocket; FIX logon credentials per session; permissions scoped per key or session.
- Venue adapter interface
Order entry, amend and cancel; order and fill events; balance queries; open order and fill recovery; rate limit accounting; error code mapping. Clients with source access can build adapters against the same interface.
- Venue keys
Stored encrypted in your environment in a self-hosted install. Keys are used only by the adapter that needs them and are never written to logs.
- Connected venues
See the Integrations page. Each entry shows its status, and only reviewed connections are listed as confirmed.
05 / Controls and audit
What you configure, and what gets written down
Configurable
- Session and API credentials per connection
- Accounts and permissions per credential: trade, view, or both
- IP allowlists and FIX session credentials
- Limits per connection
- Cancel on disconnect per session
- Drop copy sessions per account or firm
Logged to the audit trail
- credential created · accounts and permissions
- session logon and logout
- disconnect and reconnect · sequence recovery
- message reject · reason
- connection enabled for production
- permission change · old and new scope, user
06 / Where it fits
- Works on its own
- Yes, as the unified exchange API: one FIX or REST gateway to many venues for firms that keep their own OMS.
- Needs the core
- The client-facing FIX gateway for your own clients, with sessions, drop copy and per-client permissions, runs on the core platform.
- Who uses it
- Engineering teams at every client type; brokers and exchanges offering FIX access to their own clients; fintechs integrating a front end.
FAQ
Questions we get asked
Which FIX version do you support?
FIX 4.4 for order entry, drop copy and market data. If your clients need a specific dialect or custom tags, we document them in the session's rules of engagement.
Can our own clients connect to us over FIX through Qubit?
Yes. With the core platform, you can offer FIX sessions to your clients under your brand, each with its own accounts, limits and drop copy.
How do you handle exchange API changes?
Adapters are updated in our release cycle and delivered with maintenance releases. Breaking venue changes are prioritized. Self-hosted clients choose when to apply releases.
Is there an SDK?
The APIs are documented with examples on the Developers page. Client libraries are planned; until then, any standard FIX engine and HTTP and WebSocket client will work.
Give your engineers one integration instead of many
A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.