All trades
What is this endpoint for?
Tick-level data is the most granular level of trading data, and contains every single trade that occurs or centralized and decentralized exchanges. The data is normalized and timestamped and contains information such as the price and volume of each trade. For DEX’s specifically, we also provide additional information on the user address, the blockchain, the pool address and transaction hash related to the trade.
Endpoints
gateway-v0-grpc.kaiko.ovhgateway-v0-http.kaiko.ovhhttps://gateway-v0-http.kaiko.ovh/api/stream/market_update_v1Request parameters
instrumentCriteria
A nested object to configure following properties for your stream:
exchange(String) - The code(s) for the exchange(s)instrument_class(String) - The class(es) of the instrument(s) .code (String) -The Kaiko code for the instrument.
Explore instruments, codes and exchanges in the Instrument Explorer or Reference Data.
cbse
spot
btc-usd
commodities
Must always be [pb_commodity.SMUC_TRADE]
[pb_commodity.SMUC_TRADE]
interval
For accessing 72h replay data only. See the replay code example.
start_time
end_time
Response fields
additionalProperties
Additional properties, specific to the exchange.
amount
Quantity of asset bought or sold (can be in base_asset, quote_asset or the number of contracts).
class
Instrument class, empty when not mapped.
code
Instrument code, empty when not mapped.
exchange
Instrument exchange code.
sequenceId
Sequence ID for event. Sortable in lexicographic order.
id
Trade ID, empty string when not present.
price
Price for the trade.
tsExchange
The timestamp provided by the exchange for the transaction.
tsCollection
The timestamp for when Kaiko received the trade from the exchange.
tsEvent
The timestamp the data became available in the Kaiko system.
side
- UNKNOWN: Unknown side (not specified). - BUY: Buy side. - SELL: Sell side. See "taker_side_sell" Explained
Request examples
This example demonstrates how to request historical data using replay. The maximum amount of data you can request for one replay cannot exceed a total of 24 hours in hours, seconds, and minutes.
Replay data is available on a 72-hour rolling basis and should only be used to retrieve missed data. If full history is required, please use Rest API or CSV deployment methods.
cURL requests are intended for testing purposes only.
For more advanced users, you can access our full SDK here, where you'll find more coding languages, examples and guidance.
Response Example
Last updated
Was this helpful?
