Bithumb API

Name: Bithumb API API
Brand: Bithumb API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer24 EndpointsREST

For Agents

Read Bithumb market data (tickers, order books, candles) and place authenticated trades on the Korean crypto exchange. 24 endpoints across legacy and v1 surfaces, bearer token authentication.

Quickstart

Get started with Bithumb API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get the latest btc krw ticker on bithumb"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bithumb API API.

Read the latest ticker for a Korean Won pair via /public/ticker/{order_currency}_{payment_currency} or /v1/ticker

Pull the order book for a symbol via /public/orderbook/{order_currency}_{payment_currency}

Retrieve recent transactions for a symbol via /public/transaction_history

Fetch OHLC candles at minute, day, week, or month granularity via /v1/candles/* endpoints

GET STARTED

Start building with Bithumb API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Bithumb API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bithumb API, keeping it validated and agent-ready. Bithumb is South Korea's leading cryptocurrency exchange. The unified API covers both the legacy public surface under /public and the newer v1 surface under /v1, providing tickers, order books, transaction histories, and OHLC candles at minute, daily, weekly, and monthly granularity. Authenticated v1 and v2 endpoints support trading, account management, and KRW-denominated workflows specific to the Korean market.

Use Cases

Patterns agents use Bithumb API API for, with concrete tasks.

★ Korean Won market data ingestion

Crypto research teams ingest KRW-denominated market data because the Bithumb book often diverges from USD venues during local market hours, creating arbitrage signals known as the Kimchi Premium. The /public/ticker, /public/orderbook, and /v1/candles endpoints return this data without authentication, so a scheduled job can pull tickers every minute and write them to a research warehouse.

Pull 1-minute candles for BTC_KRW over the last 60 minutes via /v1/candles/minutes/1 and write them to the research warehouse

Multi-venue arbitrage feed

Traders building a multi-venue arbitrage feed include Bithumb because the KRW book frequently quotes a different price than USD venues. The /public/ticker endpoint returns the closing, opening, high, low, and volume fields needed for cross-venue spread monitoring, and /v1/orderbook gives the depth needed to size an arbitrage trade. Refresh cadences of 1-5 seconds are typical and stay within published rate limits.

Every second, pull /public/ticker for BTC_KRW and compare the close field to the BTC_USDT close on another venue; alert when the spread exceeds 2 percent

Authenticated trading on the v1 private surface

Korean residents and licensed entities place orders on Bithumb's v1 private endpoints using a bearer token tied to their account. The same OpenAPI surface that exposes the public market data also describes the authenticated trading operations, so the same client library can read tickers and submit orders. KYC and Korean banking onboarding sit outside the API surface and must be completed in the Bithumb UI first.

After KYC, submit a limit buy order on BTC_KRW at 1 percent below the current ticker close and confirm acknowledgement

Agent integration via Jentic for Korean crypto market data

An AI agent that needs a Korean Won price reference calls Jentic with the intent 'get a btc krw price'. Jentic returns the Bithumb /public/ticker operation with its path-parameter schema. For authenticated calls, the bearer token stays in the Jentic vault and is injected at execution time, so the agent can place an order without ever holding the secret.

Search Jentic for 'get btc krw ticker', load the public ticker schema, and execute against order_currency=BTC, payment_currency=KRW

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for bithumb api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/public/ticker/{order_currency}_{payment_currency}

Return the latest ticker for a KRW pair on the legacy public surface

GET

/public/orderbook/{order_currency}_{payment_currency}

Return the order book for a KRW pair

GET

/public/transaction_history/{order_currency}_{payment_currency}

Return recent transactions for a KRW pair

GET

/v1/market/all

List the full set of supported markets

GET

/v1/candles/minutes/{unit}

Return minute-granularity OHLC candles

GET

/v1/candles/days

Return daily OHLC candles

GET

/v1/ticker

Return the v1 ticker for a market

GET

/v1/trades/ticks

Return recent v1 trade ticks

GET

/public/ticker/{order_currency}_{payment_currency}

Return the latest ticker for a KRW pair on the legacy public surface

GET

/public/orderbook/{order_currency}_{payment_currency}

Return the order book for a KRW pair

GET

/public/transaction_history/{order_currency}_{payment_currency}

Return recent transactions for a KRW pair

GET

/v1/market/all

List the full set of supported markets

GET

/v1/candles/minutes/{unit}

Return minute-granularity OHLC candles

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bithumb bearer tokens are stored encrypted in the Jentic vault. Jentic builds the Authorization header at execution, so agent prompts and logs never contain the raw token.

Intent-based discovery

Agents search by intent (e.g. 'get btc krw ticker' or 'list bithumb markets') and Jentic returns the matching public or authenticated operation with its input and response schema.

Time to first call

Direct Bithumb integration: 1-3 days to implement bearer auth, handle the dual /public and /v1 surfaces, and manage rate limits. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Binance API

Global crypto exchange with broader symbol coverage and USDT pairs.

Choose Binance when the agent needs USDT-denominated pairs or broader liquidity than the KRW book.

Alternative

Kraken API

US-friendly exchange with comparable REST trading and market data.

Choose Kraken when the user needs USD or EUR fiat pairs rather than Korean Won.

Alternative

Bitfinex API

Established exchange with USD pairs and a deep margin book.

Choose Bitfinex when the agent needs USD pairs and authenticated margin trading.

Complementary

Bittrex API

Secondary exchange useful as a cross-venue reference for arbitrage feeds.

Use Bittrex alongside Bithumb when the agent runs a multi-venue arbitrage feed across regions.

FAQs

Specific to using Bithumb API API through Jentic.

Why is there no official OpenAPI spec for Bithumb API?

Bithumb does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bithumb API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bithumb API use?

Authenticated endpoints use HTTP Bearer tokens. Each call sets Authorization: Bearer {token} on the request. Public market data endpoints under /public and /v1 do not require any credential. Through Jentic the token is held encrypted in the vault and injected at execution time.

Can I read KRW market data without an account?

Yes. The /public/ticker, /public/orderbook, /public/transaction_history, /v1/market/all, /v1/candles/* and /v1/ticker endpoints are all public. They return Korean Won pair data without authentication, so a research pipeline can pull tickers and candles without onboarding.

What are the rate limits for the Bithumb API?

Bithumb's documentation publishes per-IP rate limits in the low single digits per second on the public endpoints, with tighter limits on authenticated routes. A 429 response indicates the limit was hit; back off with exponential delay before retrying.

How do I get a BTC_KRW price through Jentic?

Run pip install jentic, search Jentic for 'get btc krw ticker', load the /public/ticker operation schema, and execute with order_currency=BTC and payment_currency=KRW. The response close field is the latest trade price.

What candle intervals does the v1 API support?

The v1 candles surface exposes minute, day, week, and month endpoints: /v1/candles/minutes/{unit}, /v1/candles/days, /v1/candles/weeks, and /v1/candles/months. The minute endpoint accepts a unit path parameter for the granularity (1, 3, 5, 15, 30, 60, 240).