Copy-trading leads and leaderboard traders from 12 exchanges and blockchains: rankings, open positions, closed positions, orders and transfers. One JSON format for all of them, and a stream that tells you when they trade.
Pick a source to see its routes and real responses. Code you write for one works on the others.
The same route on OKX and on Hyperliquid answers with the same fields. Rates are fractions, sizes are in the base asset, and what only one exchange sends sits apart in sourceDetails.
Each source offers the ones its exchange publishes.
traders14 of 16 sourcestraderSearch13 of 16 sourcestraderProfile15 of 16 sourcesperformance12 of 16 sourcestraderChart15 of 16 sourcesopenPositions15 of 16 sourcespositionHistory14 of 16 sourcesorderHistory9 of 16 sourcestransferHistory8 of 16 sourcesEvery route, parameter and response is in the reference. API reference
Subscribe once and the API polls for you. Hold a WebSocket open, or let signed webhooks POST each change to your server. Both count one request per check, however many of your clients follow the same trader.
const ws = new WebSocket("wss://api.kopyon.com/v5/stream?apiKey=" + KEY);
ws.onopen = () => ws.send(JSON.stringify({
type: "subscribe",
source: "okx-copy-trading",
topic: "positionEvents",
traderId: TRADER_ID,
}));
ws.onmessage = (m) => console.log(JSON.parse(m.data));{
"type": "events",
"source": "okx-copy-trading",
"topic": "positionEvents",
"traderId": "TRADER_ID",
"data": {
"events": [
{
"event": "opened",
"symbol": "SOLUSDT",
"side": "LONG",
"size": 620,
"position": {
"symbol": "SOLUSDT",
"side": "LONG",
"size": 620,
"entryPrice": 142.31,
"markPrice": 142.4,
"leverage": 20,
"unrealizedPnl": 55.8
}
}
]
}
}Most integrations are one of these. Compare what each exchange publishes.
Every plan reaches every source, and paid plans add the stream and webhooks. The rest is how fast you can call, how many calls you get, and what you may do with the data.
Capacity, uptime and redistribution rights are all negotiated. It's for firms reselling the data, or running it as core infrastructure.
As fresh as the exchange publishes it. Each request is read from the source when you make it; identical requests in the same second share one read. Exchanges refresh on their own schedule, from about a second to several minutes, and each route's reference says how often where we know it.
Yes. A free key gets 10,000 requests a month on every source and never asks for a card, and the console has a playground that runs any route or stream with your key. Without a key, each IP gets 10 calls a day per route.
Yes. Every source answers the same routes with the same field names: traders, traderProfile, openPositions, positionHistory and so on. Rates are fractions, sizes are in the base asset, and rankings page with page while histories page with a cursor. What only one exchange sends goes in sourceDetails.
You subscribe to a topic for one trader, and the API polls the exchange for you and sends only what changed: a WebSocket message, or a signed POST to your URL. Each poll counts one request, shared by all your connections and webhooks on the same trader. They come with every paid plan.
The answer says so with hidden: true and an empty list, rather than an empty list you would read as closed, and the stream sends a hidden message instead of closing everything.
No. Kopyon reads what traders share publicly on each exchange or blockchain. A few sources, such as OKX, Hyperliquid and dYdX, publish it through documented APIs; the rest through their websites. An exchange can change what it publishes, and the changelog in the reference says when that affects a route.
Yes. Dedicated plans negotiate limits, capacity and the right to redistribute the data. Tell us the volume you need on Telegram at @nunnito, or by email.
The free tier is 10,000 requests a month. That is enough to build a whole integration and test it against live data before you pay anything.
Usually answered within a day · [email protected] ·