canonical: https://jentic.com/apis/bittrex.com/bittrex # Bittrex API v3 Jentic publishes the only available OpenAPI specification for Bittrex API v3, keeping it validated and agent-ready. The Bittrex API v3 covers the full surface of the Bittrex cryptocurrency exchange: public market data (markets, tickers, order books, trades, candles), authenticated trading (place, list, and cancel orders), balances, and deposit/withdrawal flows. Note that Bittrex ceased operations in December 2023, so the spec is most useful as a historical reference, a template for similar exchanges, or a target for replaying historical data - production live trading is no longer possible. ## For AI agents Historical reference spec for the Bittrex v3 exchange API: 25 endpoints covering market data, orders, balances, and deposit/withdrawal management. Bittrex ceased operations in December 2023, so this is reference-only. ## Scope Does not handle live trading after December 2023, fiat banking, or tax reporting - use for historical Bittrex schema reference only. ## Capabilities - List Bittrex markets and look up tickers, summaries, and order books for any pair - Pull recent trades and candle data for historical analysis of Bittrex pairs - Place, list, and cancel orders through the orders endpoints (when the exchange was live) - Inspect balances per currency on a Bittrex account - Request and list deposit addresses for incoming crypto transfers - Initiate and track withdrawals to external wallet addresses ## Use cases ### Historical Market Data Reference Use the Bittrex v3 spec as a structured reference for historical market data analysis. Endpoints like /markets, /markets/{marketSymbol}/orderbook, and /markets/{marketSymbol}/candles/{candleType}/{candleInterval}/recent describe the data shapes that historical data dumps follow. Quants and researchers can use the spec to deserialise archived Bittrex data without reverse-engineering payload formats. Example prompt: Read the schema for /markets/{marketSymbol}/candles/{candleType}/{candleInterval}/recent from the spec and use it to parse a stored Bittrex candle dataset into typed records. ### Exchange Integration Template Treat the Bittrex v3 spec as a template when building integrations for similar centralised exchanges. The 25 endpoints follow standard exchange patterns - markets, tickers, orderbook, trades, candles, balances, orders, addresses, withdrawals, deposits - so the data model is reusable for adapter design. This shortens the design phase of a new exchange connector. Example prompt: Generate stub method signatures from the Bittrex v3 paths and reuse them as the interface for a new exchange adapter. ### Migration Audit for Former Bittrex Users Teams that previously integrated with Bittrex use the spec to audit which calls their codebase relied on, then map each operation to an equivalent endpoint on a live exchange. The spec exposes the exact paths and parameters the legacy integration used, so a migration plan can be produced without reading the original code line by line. Example prompt: List every operationId in the Bittrex v3 spec and propose a target endpoint on a live exchange for each. ### Agent Discovery via Jentic An AI agent investigating historical crypto market structure searches Jentic for Bittrex market or ticker operations. Jentic returns the matching Bittrex v3 operation with its schema, which the agent uses to interpret archived response payloads or document data shapes for downstream reporting. Live calls to the production Bittrex API will not succeed, but the spec remains useful for tool discovery and schema lookup. Example prompt: Use Jentic search for 'list Bittrex markets', load the schema, and use the response shape to parse a stored markets snapshot. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /markets | List Bittrex markets | | GET | /markets/{marketSymbol}/orderbook | Order book for a market | | GET | /markets/{marketSymbol}/candles/{candleType}/{candleInterval}/recent | Recent candles for a market | | POST | /orders | Place a new order | | DELETE | /orders/{orderId} | Cancel an order | | GET | /balances | List account balances | | POST | /withdrawals | Create a withdrawal | ## Key resources - **Markets** — Markets, summaries, tickers, order books, trades, and candles for Bittrex pairs - **Currencies** — Catalogue of currencies that traded on Bittrex - **Balances** — Per-currency account balances - **Orders** — Place, list, and cancel orders (open and closed) - **Addresses** — Deposit address management - **Withdrawals and Deposits** — Initiate withdrawals, list withdrawal and deposit history ## Why Jentic - **Setup:** Bittrex is offline, so wiring this v3 API by hand would still mean setting the API-key header and HMAC inputs and targeting the api.bittrex.com/v3 host only to reach a dead endpoint. Through Jentic you install once, import Bittrex from the API Directory as a schema reference, and your agent reads the archived operations instead of attempting a live call. - **Permission scoping:** Bittrex puts the market symbol and order id in the URL path (/markets/{marketSymbol}/orderbook, /orders/{orderId}), so a rule can pin your agent to one market for reads: it can read that market's order book and candles and nothing else. You choose the operations it may call, so order placement or withdrawals are not included unless you add them, and the exchange is offline in any case. - **Credential handling:** Any archived Bittrex key and signing secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context, though the live endpoint is offline. - **Discovery method:** Agents search Jentic by intent such as 'list Bittrex markets' or 'get a Bittrex order book', and Jentic returns the matching v3 operation with its input and response schema so the agent reads the reference without browsing the docs. ## Related APIs - **Bitstamp API** — Bitstamp is a live crypto exchange - the natural live target if you are migrating away from Bittrex. - **BizToc** — BizToc supplies business and crypto news that contextualised Bittrex price moves before the shutdown. - **Blackfire.io** — Blackfire profiles applications that previously polled Bittrex and now need to be retargeted. ## FAQ ### Why is there no official OpenAPI spec for Bittrex API v3? Bittrex did not publish an OpenAPI specification, and the company ceased operations in December 2023. Jentic generates and maintains this spec so AI agents and developers can read the historical interface via structured tooling. Get started with Jentic One, the self-hosted execution layer. ### Is the Bittrex API v3 still live? No. Bittrex ceased operations in December 2023, so calls to https://api.bittrex.com/v3 will not return live data. The spec is useful as a structured reference for historical data analysis, integration templates, and migration audits to other exchanges. ### What authentication does the Bittrex API v3 use? The spec defines an API-Key header (security scheme ApiKeyAuth) and notes that requests also require API-Timestamp, API-Content-Hash (SHA512 of body), and API-Signature (HMAC-SHA512 of the pre-sign string). When invoked through Jentic these credentials are stored in the encrypted vault rather than the agent context. ### Can I use the Bittrex API v3 to place orders today? POST /orders is documented in the spec, but the production Bittrex matching engine is offline. You cannot place a live order. Use the spec to model order placement against an active exchange instead. ### What are the rate limits for the Bittrex API v3? Bittrex previously enforced a global rate limit roughly equivalent to 60 requests per minute per IP, with stricter limits on authenticated trading endpoints. Since the API is no longer live, these limits are historical reference only. ### How do I look up a Bittrex market with this spec through Jentic? Install with pip install jentic, then use Jentic search with 'list Bittrex markets'. Jentic returns the GET /markets operation and its schema, which you can use to parse stored Bittrex response data even though live calls no longer return. ### Can I limit what my agent is allowed to do with the Bittrex API v3? Yes. Jentic One is self-hosted, so your own rules decide which Bittrex operations and credentials the agent can use. Because Bittrex puts the market symbol and order id in the URL path, such as GET /markets/{marketSymbol}/orderbook and /orders/{orderId}, you can pin the agent to a single market for read-only work like fetching order books and candles. Order placement (POST /orders) and withdrawals (POST /withdrawals) stay out of scope unless you explicitly grant them.