API
An API (application programming interface) is a set of rules one program uses to request data or an action from another: which URL to call, what to send and what format the response comes in. A trader needs an API when prices, order books and funding rates have to be read by a program: a bot, a spreadsheet or a dashboard.
Request example
Hypothetical example: a program asks Genesis API for the IRYS coin profile through the Coin Search endpoint. The request is an HTTP GET, with the key in a header:
curl "https://api.genesisarbitrage.com/v1/coins/search?query=IRYS" \
-H "X-API-Key: $GENESIS_API_KEY"
The response comes back as JSON, with some fields omitted:
{
"coin": "IRYS",
"contracts": [
{
"address": "0x91152b4ef635403efbae860edd0f8c321d7c035d",
"network": "BNB Smart Chain(BEP20)",
"exchanges": ["MEXC", "Ourbit"]
}
],
"exchanges": {
"MEXC": {
"spot_price": 0.01329,
"futures_price": 0.0133,
"deposit": true,
"withdraw": true
}
}
}
A person would piece this together from exchange pages and a block explorer; a program gets it in one response and can compute right away that MEXC futures trade above spot by (0.0133 − 0.01329) / 0.01329 × 100 ≈ 0.075%.
Public and private exchange APIs
An exchange API has two parts. The public part serves market data (quotes, order books, trades) without a key. The private part works with your account (balances, orders, trade history) and requires an API key plus a request signature. On Binance, public endpoints have the security type NONE; all others require a key and a signature parameter.
Data arrives in two ways. A REST API answers each request separately: that is how you get a snapshot of the data with the filters you need. A WebSocket keeps the connection open and the server pushes updates on its own: this is how Binance streams trades and order book changes in real time.
Data APIs: many venues in one response
An exchange API only knows its own venue. To compare a coin's price on 20 exchanges, a program needs 20 connections, and every exchange has its own response format and limits. A data API combines the venues in advance.
| API type | What it returns | Access |
|---|---|---|
| Public exchange API | Quotes, order books and trades of one exchange | No key |
| Private exchange API | Balances, orders, withdrawals | Key and signature |
| Genesis API | Spreads, order books, funding, DEX, on-chain, prediction markets | Key, read-only |
One request to the Genesis API /arbitrage/spot-spot endpoint returns computed spreads between the spot markets of 20+ CEX exchanges, with deposit and withdrawal flags. Every request is an HTTP GET, every response is JSON, and the parameters and fields of each endpoint are in the documentation.
See also: crypto APIs: types and how to choose, quickstart in the docs, rate limit, lesson: what a crypto API is.
Questions and answers
Do I need an SDK to work with an API?
If the API speaks HTTP, any HTTP client will do. For Genesis API, curl, requests in Python or the built-in fetch in JavaScript are enough.
Can I trade through Genesis API?
No. Genesis API only serves data. Orders are placed on the exchange by hand or through the exchange's own API with its key, at your own risk.