Integration Overview
Senticore exposes several integration surfaces. They share the same canonical sequencer, matching engine, risk checks, WAL, recovery model, and settlement guarantees; the difference is the client contract and operational tier.
Choose your path
| You are building | Start here | Then verify |
|---|---|---|
| App — a wallet-connected web or mobile product | Getting Started | Authentication, private WebSocket, and Error Model |
| Bot — an automated trader or backend service | Runnable examples | Local signing, nonces, and recovery help |
| Market maker — a quoting engine or existing OMS | Market Maker Start | Live verification, connectivity bundle, then account conformance |
The five-minute lane chooser gives the shortest overview when you have not selected a surface yet. Before relying on any production path, check current status and availability.
For liquidity providers, quote engines, and HFT-style clients, start with the Institutional Lane Parity page, read the Live Verified Beta page, then read the FIX/BSL/FIXP Connectivity Bundle, then use the Market Maker Beta Quickstart. The verification page lists what was tested against the live beta; lane parity defines which functions are expected to exist across HTTP BSL, BSL Direct TCP, FIX 4.4, and FIXP/SBE; the connectivity bundle gives direct endpoints and FIX CompIDs; the quickstart lists the route bundle to implement.
API Surfaces
| Surface | Best for | Protocol | Access |
|---|---|---|---|
| Public Market Data HTTP | Apps, dashboards, data consumers | JSON over HTTPS | Public |
| Trading HTTP | Retail traders and app backends | JSON over HTTPS | Wallet or delegated signature |
| Public WebSocket | Real-time market data | JSON over WSS | Public |
| Private WebSocket | Account, order, fill, and risk streams | JSON over WSS | Private session token |
| FIX Gateway | OMS, quant funds, institutional desks | FIX 4.4 over TCP/TLS | Self-service bundle plus institutional_agent HMAC |
| BSL Direct TCP | Market makers and quote engines | Native TCP/TLS binary order entry | Signed action frame/group, institutional_agent session state, optional lane key |
| BSL Business Line API | Market makers and quote engines | Compact HTTP compatibility plus protected reads | Signed action, optional lane key, institutional_agent HMAC |
Older MM and binary names are compatibility route names. BSL is the
canonical business-line product name.
Quick Decision Guide
| If you are building... | Start with |
|---|---|
| A web or mobile application | Public/Trading HTTP plus WebSocket |
| A retail or backend trading bot | Trading HTTP with local action signing |
| A market maker or liquidity provider | Live Verified Beta, FIX/BSL/FIXP Connectivity Bundle, then Market Maker Beta Quickstart |
| An existing OMS | FIX/BSL/FIXP Connectivity Bundle, then FIX session/order-entry docs |
| A low-latency taker strategy | BSL/FIX after a live conformance run for your account |
Common Concepts
Every surface shares:
- canonical signed actions for wallet or delegated credential authorization,
- domain-separated action hashes for deterministic encoding across clients,
Idempotency-Keyheaders for retriable HTTP mutations,clientOrderIdfor strategy-level order correlation where the path carries it,- a windowed nonce per account so orders can be pipelined without ack-blocking,
- rate-limit envelopes per surface and tier,
- stable error envelopes where available, with raw server payloads preserved during private beta.
What Not To Do
- Do not treat
/api/v1/institutional/*as the market-maker order-entry path. - Do not assume
fullBSL hotpath results are enabled for every account until your account passes a live conformance run. - Do not use owner wallet private keys inside quote engines; use delegated signing or machine credentials.
- Do not send BSL Direct TCP frames to an HTTPS/Cloudflare URL; use the bundle host, port, and TLS SNI.
- Do not build strategy state from periodic private reads when a private stream or FIX drop-copy is provisioned.