HTX Spot Public market data JavaScript example for the Siebly HTX SDK, covering exchange REST API and WebSocket integration, setup, and production SDK docs.
We use environment variables in our examples for API keys. It is your responsibility to manage and secure your keys appropriately.
@siebly/htx-api instead of hand-written HTTP request plumbing.HTX/Spot/Public/marketData.ts.SpotClient.getTimestamp(), getMarketStatus(), getTradingSymbols(), getTicker(), getTickers(), getMarketDepth(), getKlines(), getLastTrade(), getHistoryTrades().import { SpotClient } from '@siebly/htx-api'; // This example shows how to call HTX Spot API endpoints with Node.js or TypeScript// using the npm module "@siebly/htx-api" for PUBLIC MARKET DATA (no authentication). // Public calls do not require API keysconst client = new SpotClient(); async function publicCalls() { try { const timestamp = await client.getTimestamp(); console.log('Server Timestamp: ', timestamp); const marketStatus = await client.getMarketStatus(); console.log('Market Status: ', marketStatus); const symbols = await client.getTradingSymbols(); console.log('Trading Symbols: ', symbols); const ticker = await client.getTicker({ symbol: 'btcusdt' }); console.log('Ticker (btcusdt): ', ticker); const tickers = await client.getTickers(); console.log('All Tickers: ', tickers); const orderBook = await client.getMarketDepth({ symbol: 'btcusdt', depth: 10, type: 'step0', }); console.log('Order Book: ', orderBook); const klines = await client.getKlines({ symbol: 'btcusdt', period: '1min', size: 10, }); console.log('Klines: ', klines); const lastTrade = await client.getLastTrade({ symbol: 'btcusdt' }); console.log('Last Trade: ', lastTrade); const historyTrades = await client.getHistoryTrades({ symbol: 'btcusdt', size: 10, }); console.log('History Trades: ', historyTrades); } catch (e) { console.error('Error: ', e); }} publicCalls(); We use essential cookies and optional analytics. Read the Privacy Policy.
Essential cookies stay on. Toggle analytics if you want to share anonymous usage insights. You can revisit this anytime via Cookie Settings in the footer.