Historical v3 API Changes

This list includes changes prior to 9/1/21. Recent changes are listed here.

05/26/2021

  • All non-corporate users are now required to provide basic source of funds information. If you have not provided this information, you will be prompted to do so when logging into the website or mobile app. Operations related to trading or moving funds will fail with error code SOURCE_OF_FUNDS_REQUIRED if this information has not been provided. This will also be reflected in GET /account with an entry in the (new) actionsNeeded array and in the actions indicated as allowed by the permissions API.
  • You can now get your current trading fees using GET /account/fees/trading

04/09/2021

  • You can now get an execution by id
  • Miscellaneous clarifications and additional error codes documented
  • Updated known issues list

02/18/2021

  • The marketSybol included in the execution socket updates was changed to Base-Quote format to match the rest of the API.

02/16/2021

  • Updated known issues and upcoming breaking changes to reflect executions socket stream marketSymbol issue
  • Added more codes to the error code documentation

12/02/2020

  • There is now a socket stream for executions! As well as a corresponding set of REST endpoints for retrieving historical executions and synchronizing.
  • You can now place or cancel multiple orders with a single request using the /batch endpoint
  • Determining which markets and currencies you have access to can now be done more easily and explicitly via the market permissions and currency permissions endpoints
  • It is now possible to retrieve market candles based on the midpoint between best bid ad ask in addition to candles based on trade prices (note that midpoint candles from prior to 12/2 are not available)
  • The /withdrawals/whitelistAddresses endpoint has been renamed to /withdrawals/allowed-addresses for clarity. The old name will continue to work.

09/23/2020

  • You now cancel all of your open orders or all of your open orders on a market with DELETE /orders/open
  • Websocket stream for conditional orders is now available
  • Withdrawal requests can now be made idempotent by specifying a clientWithdrawalId
  • Simple examples of authenticating and subscribing to the websocket in C#, Node.js, Python, and Java may be found in the Examples section
  • Currency model now contains Bittrex's blockchain base address
  • Currency and Market models now reference any additional required terms of service agreeements

06/17/2020

  • The v3 API has reached generally availability and is ready for production use!

  • You can now get the list of executed trades related to your orders from GET /orders/{orderId}/executions

  • End of life for the v1 api is planned for 9/30/2020

06/10/2020

  • The baseVolume property was removed from MarketSummary and Candle responses. Use the quoteVolume property for quote volume or the volume property for base volume.

05/27/2020

  • Successful cancel withdrawal response will change from 204 with no content in the response body to a 200 with the cancelled withdrawal in the response body
  • Historical candles endpoint will no longer allow you to specify more portions of the date parameters than are necessary for the selected candle interval. Specify only year for day candles. Specify only year and month for hour candles.
  • GET /candles endpoint is deprecated and has been removed from the documentation. Use GET /candles/{interval}/recent instead. The response model is the same.

05/15/2020

  • v3 socket is now in public beta
  • May now trigger ceiling orders from conditional orders
  • Order object now includes the order's OCO partner (if applicable)
  • May now get whitelisted withdrawal addresses from /withdrawals/whitelistAddresses
  • Balance object now has an updatedAt timestamp
  • Markets and currencies now indicate if they are prohibited from use by US customers
  • You can now get your accountId from the account endpoint
  • Deposit object now includes whether a deposit source was blockchain, wire transfer, or credit card

01/27/2020

  • Conditional orders (e.g. stop loss) have been added to the V3 API Beta. See the new Placing Conditinal Orders section below for additional information.

  • Historical candles are now available in the API

  • The functionality of the existing candles endpoint has been duplicated into a candles/.../recent endpoint. The existing one will be retired in a future release.

08/08/2019

  • You can now use the v3 API to retrieve the bid/ask/last for all markets at once by getting v3/markets/ticker instead of querying each market individually.

  • When getting currency information from v3/currencies the response will now include a URL for an image containing the currency's logo.

06/26/2019

  • Ceiling Sell orders have been added to the V3 API Beta. This option allows you to instruct the system to sell enough of the base currency to increase your account balance of the quote currency by the specified amount.

04/19/2019

We are thrilled to announce that the v3 Beta API is now available to the public! This brand new API adds the most-requested features in a single API. Some of the highlights include:

  • Market orders to buy/sell a quantity of a currency at the best, currently available price
  • Post-only orders which allow market makers to ensure their orders are making it to the order book instead of matching with a preexisting order
  • Fill or Kill and Immediate or Cancel order types which force orders to be filled immediately or not at all
  • Client-specified order IDs for easier tracking of orders and idempotency of order placement
  • More details are available about the status of deposits and withdrawals
  • Full history of your orders and withdrawals (not just most recent 20 or 200)
  • Changed how market identifiers are structured to better align with foreign exchange trading standards (for example, the market formally known as BTC-ADA is now ADA-BTC in the v3 API)

Reaching the Beta milestone represents our confidence in the quality and stability of our new API, but we're not done adding features. You can look forward to us adding even more to this API in upcoming releases.