Exchange APIs, one guide

Create keys safely on Gate.io, OKX and Bybit — read-only first, withdrawals never — then plug them into our engine or your own code. Written from running real bots against all three APIs, not from marketing pages.

Gate.io API

v4 REST + WebSocket · spot, futures and the only public CFD/TradFi API of the three

Public market data needs no key at all — candles, tickers, order books.
Futures and spot are separate API namespaces with separate rate budgets.

Read the Gate.io API guide →

OKX API

v5 统一 REST + WebSocket · 跨现货、合约和期权的统一账户模型

v5 将现货/保证金/合约/期货/期权统一在一个账户和一个 API 下。
跟单交易有官方公共端点——它支持我们的 OKX 排行榜页面。

Read the OKX API guide →

Bybit API

v5 unified trading account · testnet included · CFD-style TradFi pairs on derivatives

v5 merges spot + derivatives into the Unified Trading Account API.
A real testnet (not a flag) is the cleanest sandbox of the three exchanges.

Read the Bybit API guide →

MEXC API

现货v3 + 合约v1 · 最广泛的小市值上币 · 公共端点对服务器IP开放

现货v3（api.mexc.com）和合约v1（contract.mexc.com）是独立的API，具有独立的基URL。
公共市场数据无需密钥，直接响应数据中心IP——与交易所网页不同。

Read the MEXC API guide →

Connect keys to our engine. Read-only keys give you a live portfolio view across exchanges. Trade-enabled keys — after our access gate — run researched presets on your own account. Keys are stored encrypted; any key with withdrawal permission is refused. Start at /app/start.

Building on our research data instead of exchange APIs? That is a different product: the Tvijo AIOS Intelligence API. Fees for trading through these APIs are compared on the fees page.