Crypto exchange API

A crypto exchange API for traders, market makers and your own apps

Everything a user can do on your website is available through the API: market data, orders, futures, wallets and account data. Traders connect their bots with keys limited to the permissions and IP addresses they choose.

REST API v1 WebSocket feeds Read, trade, withdraw scopes IP whitelists
Who uses it

One API, several audiences

An exchange API is not only for developers. These are the people who will rely on yours.

Algo traders

Run their own strategies against your markets with trade-only keys.

Market makers

Quote both sides of your books and react to fills over the live feed.

Data sites

CoinMarketCap, CoinGecko and portfolio trackers read your prices and volume.

Your own apps

The mobile app and any partner integration use the same endpoints.

Public data

Public market data endpoints

No key needed. Rate limits protect the server from abuse.

EndpointReturns
GET /marketsAll markets with their rules and precision
GET /markets/tickerLast price, 24h change, high, low and volume
GET /markets/orderbookBids and asks for a market
GET /markets/tradesRecent trades
GET /markets/candlesOHLC candles
GET /futures/markIndex and mark price for futures
GET /servertimeServer time for request timing

Built for real integrations

  • Versioned under /api/v1, so future changes do not break existing clients
  • Numbers returned as strings at the market's precision, never in floating-point notation
  • Times in ISO 8601 or Unix milliseconds, as documented per endpoint
  • Clear validation errors with the field and reason

Public endpoints also serve the airdrop list, VIP fee schedule, insurance fund balance and news, so a partner can build a full view of your exchange without logging in.

Trading and wallets

Authenticated endpoints

Requests with an API key act for that user and only see that user's data.

Spot trading

Place market, limit and stop orders, cancel them, and list open orders, order history and fills.

Futures

Open long or short positions with leverage, set take-profit and stop-loss, close positions and list open ones.

Wallets

Balances per coin, deposit addresses per network, deposit and withdrawal history, transfers between Funding and Trading, and withdrawals.

More

Trading bots, copy trading, margin accounts, staking, P2P and account statements are reachable through the same API.

The website and the mobile app use the same API your traders get.
WebSocket

Live feeds over WebSocket

Polling an order book every second is slow and wasteful. The WebSocket server pushes changes the moment they happen. It uses the widely supported Pusher protocol, so there are client libraries for most languages.

  • Market channel: price, change, high, low and volume for every market
  • Order book channel per market: a signal on every book change
  • Trades: new trades as they happen
  • Private user channel: order updates, fills and balance changes, authorised with the user's token

Push, not poll

Updates arrive as they happen, with less load on your server.

Private channels

Each user only receives their own orders and balances.

Self-hosted

The WebSocket server runs on your infrastructure, no paid service needed.

Standard protocol

Pusher-compatible, so existing client libraries work.

API keys

API keys users can trust with their money

A leaked API key is one of the most common ways traders lose funds. The key settings are built to limit that damage.

  • Scopes: read, trade and withdraw, chosen per key
  • IP whitelist: single addresses or ranges (IPv4 and IPv6), and requests from anywhere else are refused
  • Withdraw keys must have an IP list: a key that can move funds cannot be used from an unknown address
  • No account changes: API keys cannot change passwords, 2FA, email or other security settings
  • Withdrawals still need 2FA and respect address whitelists and security holds
  • Rate limits on every route

Users create, edit and delete keys under Account → API Management. The secret is shown once.

CMC and CoinGecko

Ready for CoinMarketCap and CoinGecko

Both sites list an exchange only after they can read its data automatically, and each asks for its own format. The platform already serves both, from the Basic package up.

Being listed there puts your exchange in front of people comparing where to trade a coin, and makes your volume and prices visible to the wider market.

CoinMarketCap

  • Markets summary
  • Ticker
  • Order book
  • Trades
  • Assets

CoinGecko

  • Pairs
  • Tickers
  • Order book
  • Historical trades
FAQ

Crypto exchange API questions

Is the trading API included in every package?

Yes. The trading API and the CoinMarketCap and CoinGecko endpoints are part of the Basic package and everything above it.

Does the exchange have a WebSocket API?

Yes. A self-hosted WebSocket server pushes market, order book, trade and private user updates using the Pusher protocol.

How are API keys secured?

Each key has read, trade and withdraw scopes and an optional IP whitelist, which is required for withdraw keys. Keys cannot change account security settings, and withdrawals still need 2FA.

Can I extend the API?

Yes. You receive the source code, and the API is a standard Laravel route file with controllers, so new endpoints follow the same patterns.

Is there documentation?

Yes. API documentation pages are part of the platform and can be published on your own domain. See the demo docs.

Ready to launch your cryptocurrency exchange or need expert support?