Crypto API Documentation - Endpoints, Examples & Quick Start
BytNode aggregates the main trading venues and many specialised providers into a single interface. Prices, derivatives, options, on-chain, ETF flows, macro and sentiment are all served there with the same conventions, the same units and the same timestamps.
Three channels, a single key: a REST API to query, a WebSocket stream to listen, an MCP server for agents.
#What a call looks like
A key in the X-API-KEY header, a route, parameters: here the latest funding rate of Bitcoin, a call that works on the free plan. From the Traders plan, /v1/snapshot returns up to forty-eight fields in one request.
curl -H "X-API-KEY: $BYTNODE_API_KEY" \
"https://api.bytnode.com/v1/funding/rate?symbol=BTCUSDT"#Where to start
Six ways in, depending on what you are trying to do.
First callFrom the API key to the first response: one request in curl, in Python and in TypeScript.AuthenticationOne API key for the three channels. Where to put it, how to protect it, how to rotate it.REST APIThe shape of a REST request, the families available and the latest / history choice.WebSocket streamFive consolidated channels, authentication at the handshake, sequences and close codes.MCP serverThree tools for AI agents, with no bespoke integration. Connection and examples.The catalogueThe ten categories, their datasets, the twenty-two assets and the eight timeframes.
#The four parts
The contents on the left follow this order, and each page leads to the next one from the bottom.
APIThe two APIs and what it takes to call them: first call, authentication, responses, limits, conventions, REST family by family, then the WebSocket stream. Access to each family depends on the plan (see /pricing).MCPThree tools for AI agents, with no bespoke integration. Connection and examples.DataThe ten categories, their datasets, the twenty-two assets and the eight timeframes.ReferenceThe full endpoint catalogue, the error codes and the metrics glossary.