Public endpoints for market data and an authenticated private API for your own services — with the source, so the API is extensible rather than fixed.
An exchange API gets used by three groups: your own services, your traders' bots, and whatever you build next. All three are easier when you can change the API.
What ships, and what you can do with it because the source comes with it.
Public API
Read access, no authentication.
- Assets and market listings
- Prices and market data
- Transaction history endpoints
Private API
Authenticated access for services and integrations you control.
- Authenticated endpoints for remote services
- Registration and KYC workflows exposed programmatically
- Scoped to the permissions you configure
Real-time and integrations
Where the API meets the rest of the stack.
- WebSocket feeds for trades and market data
- Trade socket and WebSocket server status in the monitoring panel
- Binance API and WebSocket feeds
- Payment, KYC and liquidity provider integrations
Questions you might have
Is the API documented?
Documentation is delivered with the platform, alongside configuration and deployment docs.
Can we add endpoints?
Yes. You hold the source, so the API is yours to extend.
Do traders get API access for bots?
That is a configuration decision. The private API supports it, and you set who is allowed.
See this part of the stack running
A technical demo walks the architecture with someone who deploys it. Bring your engineer — the questions that matter here are theirs.