Huobi API

Cryptocurrency / API Key Intermediate HTTPS
72 B
Measured Score 0 50 100 Speed 25/30 Consistency 13/20 Security 20/20 Browser access 10/15 Transparency 4/15 TESTED 2026-08-10

Overview

Huobi (now HTX) is a major global cryptocurrency exchange API headquartered in Seychelles, offering access to hundreds of spot and futures trading pairs. It provides real-time market depth, candlestick data, and trade history for currencies including BTC, ETH, and many altcoins. An API key is required for trading operations, but some public market endpoints can be accessed without authentication.

Beginner Tip

Start with the public market-data endpoints — such as GET /market/detail/merged — which do not require an API key, to familiarize yourself with the response structure before setting up authentication.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://api.huobi.pro/market/detail/merged?symbol=btcusdt
Result
HTTP 200 · application/json · 302 bytes
Response time
43 ms (median of 3) · fastest 36 ms
Transport
TLSv1.3 · TLS_AES_128_GCM_SHA256 · certificate issued by Amazon
Browser CORS
Allowed — Access-Control-Allow-Origin: https://apisscore.com
Served by
openresty
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
ch string market.btcusdt.detail.merged
status string ok
ts integer 1786391377679
tick object {11 fields}

Captured Response

Captured from a real request to https://api.huobi.pro/market/detail/merged?symbol=btcusdt on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "ch": "market.btcusdt.detail.merged",
  "status": "ok",
  "ts": 1786391377679,
  "tick": {
    "id": 385028572696,
    "version": 385028572696,
    "open": 65157.8,
    "close": 64030.98,
    "low": 63838.46,
    "high": 65438.59,
    "amount": 2492.707268472641,
    "vol": 161611008.4192694,
    "count": 21421,
    "bid": [
      64034.55
    ],
    "ask": [
      64034.56
    ]
  }
}

Field Reference

status Indicates request success; "ok" means data is valid.
ts Server-side timestamp in milliseconds when the data was captured.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://api.huobi.pro/market/detail/merged?symbol=btcusdt";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 404 Requesting a path that does not exist unknown
404 Not Found

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

invalid-parameter (bad symbol) Huobi symbols are lowercase and concatenated, so using the wrong format causes rejection.
Use lowercase pairs like "btcusdt" (not "BTC/USDT" or "BTC_USDT") in the symbol query parameter.
Signature verification failed The HMAC-SHA256 request signature is incorrectly computed when calling private endpoints.
Ensure you sort parameters alphabetically before signing, and include the timestamp in UTC ISO-8601 format.
429 Too Many Requests Exceeding the rate limit, which differs for public (10 req/sec) and private (5 req/sec) endpoints.
Implement exponential backoff and track your request count per second; use websocket streams for real-time data instead of polling.

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 25/30
Consistency 13/20
Security 20/20
Browser access 10/15
Transparency 4/15
Endpoint Response Time 43ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS UNKNOWN
Category Cryptocurrency
Difficulty Intermediate
Endpoint last called: 2026-08-10

Similar APIs

View All →