Bithumb APIfeed.bithumb.com ↗
Access Bithumb Korea market tickers, order books, candlestick OHLCV, transaction history, and official notices via 13 structured API endpoints.
What is the Bithumb API?
The Bithumb Feed API provides 13 endpoints covering real-time KRW and BTC market data from Bithumb Korea, plus the exchange's official content feed. Endpoints like get_ticker return opening, closing, min, max, and 24-hour volume figures for any trading pair, while get_candlestick delivers OHLCV arrays at configurable intervals. Content endpoints cover notices, press releases, and trend reports with full HTML body text and pagination.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/a05f54db-d107-4dfe-9f49-55037ab2b2aa/get_all_tickers_krw' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace feed-bithumb-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Bithumb Korea — market data and feed content walkthrough."""
from parse_apis.bithumb_korea_public_market_data_api import (
Bithumb,
CandlestickInterval,
PaymentCurrency,
ContentNotFound,
)
client = Bithumb()
# Fetch a single ticker for BTC/KRW — direct typed field access.
ticker = client.tickers.get(order_currency="BTC", payment_currency=PaymentCurrency.KRW)
print(ticker.closing_price, ticker.fluctate_rate_24H)
# Browse recent notices with keyword filter — limit= caps total items fetched.
for notice in client.notices.list(keyword="BTC", limit=3):
print(notice.title, notice.publication_date_time)
# Drill into one notice for its full HTML content and attachments.
notice = client.notices.list(limit=1).first()
if notice:
detail = notice.details()
print(detail.title, detail.board_type, len(detail.attachfile_list), "attachments")
# Trend reports — market analysis articles.
for report in client.trendreports.list(limit=3):
print(report.title, report.publication_date, report.category)
# Typed error handling: catch ContentNotFound on a bad ID.
try:
first_notice = client.notices.list(limit=1).first()
if first_notice:
d = first_notice.details()
print(d.title)
except ContentNotFound as exc:
print(f"Content not found: {exc}")
print("exercised: tickers.get / notices.list / notice.details / trendreports.list")
Fetch all KRW market trading tickers. Returns current price, volume, and fluctuation data for every cryptocurrency pair traded against KRW.
No input parameters required.
{
"type": "object",
"fields": {
"BTC": "ticker object for Bitcoin with opening_price, closing_price, min_price, max_price, units_traded, etc.",
"ETH": "ticker object for Ethereum",
"date": "timestamp string"
},
"sample": {
"data": {
"data": {
"BTC": {
"max_price": "94456000",
"min_price": "92130000",
"fluctate_24H": "2156000",
"units_traded": "292.33865804",
"closing_price": "94026000",
"opening_price": "93444000",
"acc_trade_value": "27279735681.42854",
"units_traded_24H": "536.7154315",
"fluctate_rate_24H": "2.35",
"prev_closing_price": "93444000",
"acc_trade_value_24H": "49885249780.00505"
},
"date": "1781156230894"
},
"status": "0000"
},
"status": "success"
}
}About the Bithumb API
Market Data Endpoints
get_all_tickers_krw and get_all_tickers_btc return a single object keyed by cryptocurrency symbol, giving you price and volume snapshots across every listed pair against KRW or BTC in one call. For a focused view, get_ticker accepts order_currency (e.g. BTC, ETH, SOL) and payment_currency (KRW or BTC) and returns opening_price, closing_price, min_price, max_price, units_traded, acc_trade_value, prev_closing_price, and units_traded_24H. The get_orderbook endpoint returns timestamped bids and asks arrays with price and quantity at each level for the same pair structure.
Trade History and Candlesticks
get_transaction_history returns an array of recent trades for a pair, each with transaction_date, type (ask or bid), units_traded, price, and total. get_candlestick accepts an optional interval parameter alongside order_currency and payment_currency, and returns historical arrays in [timestamp, open, close, high, low, volume] format suitable for charting or time-series analysis.
Official Content Feed
Three content families are exposed: notices (get_notices, get_notice_detail), press releases (get_press_releases, get_press_release_detail), and trend reports (get_trend_reports, get_trend_report_detail). List endpoints support page and keyword parameters; notices also accept a category filter for types such as maintenance, new services, or trading suspensions. Detail endpoints return full HTML content, categoryName1, publicationDateTime, modifyDateTime, and an attachfileList. The search_feed endpoint runs a keyword query across all three sections simultaneously, returning press, trends, and notices objects each with a totalCount and item list — useful for cross-section discovery without three separate calls.
The Bithumb API is a managed, monitored endpoint for feed.bithumb.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when feed.bithumb.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official feed.bithumb.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Building a KRW/BTC price dashboard that tracks closing_price and units_traded_24H across all Bithumb pairs in real time
- Populating order book depth charts using bids and asks arrays from get_orderbook for specific trading pairs
- Feeding candlestick OHLCV data from get_candlestick into a backtesting or technical analysis pipeline
- Monitoring Bithumb's trading suspension and maintenance notices by polling get_notices with category filters
- Aggregating Bithumb press releases and trend reports into a crypto news aggregator using content HTML and publication dates
- Alerting on new listings or service changes by searching get_notices and get_press_releases by keyword
- Comparing recent transaction history from get_transaction_history to order book depth to identify short-term market pressure
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Bithumb have an official developer API?+
What does get_candlestick return and what intervals are available?+
interval parameter. The endpoint reflects whatever intervals Bithumb's candlestick feed supports (e.g. 1m, 3m, 5m, 10m, 30m, 1h, 6h, 12h, 24h); consult the Bithumb API docs for the full enumeration of accepted values.Does the API expose private account data such as balances, open orders, or trade history for a specific user?+
How does the notice category filter work in get_notices?+
category parameter in get_notices accepts a numeric category ID. Known mappings are: 1 (안내 / general announcements), 2 (신규서비스 / new services), 3 (점검 / maintenance), 4 (업데이트 / updates), 5 (거래유의 / trading caution), 6 (거래지원종료 / trading support end), 7 (입출금 / deposits and withdrawals). Omitting the parameter returns notices across all categories.