Skip to main content
Release 24.02.2026
JSON-RPC API changes
New API method: public/get_index_chart_data is now publicly accessible.
Action required: The deprecated method private/get_pending_block_trades will be removed. Please use private/get_block_trade_requests instead.
Release 13.01.2026
JSON-RPC API changes
⚠️ New order book lifecycle - BREAKING CHANGEAs part of the Instrument Order Book lifecycle enhancement, the state field in the following methods and channels has been updated:Affected methods:Affected channels:Extended pme/simulate method with additional dataExtended private/pme/simulate API response with pre_aggregated_risk_vectors which contain aggregated_risk_vectors before applying pnl_offset and extended_dampener params
Release 16.12.2025
JSON-RPC API changes
max_quote_quantity is now required in /private/set_mmp_configThe precision of MMP configuration limits is restricted to a maximum of four decimal places.New fields were added to the responses of private/get_account_summary and private/get_account_summaries:
  • affiliate_promotion_fee (if greater than 0.0)
  • trading_products_details (which trading products are enabled or can be overwritten for the account)
  • receive_notifications
fees field structure in private/get_account_summary and private/get_account_summaries has been updated. It is now list of fee objects for all currency pairs and instrument types related to the currency. This field is visible when parameter extended = true and user has any discounts
Release 25.11.2025
JSON-RPC API changes
Breaking ChangesRemoved deprecated method public/get_index. Users are advised to use /public/get_index_price instead.Non-Breaking ChangesAdded max_quote_quantity parameter to private/set_mmp_config (when block_rfq: false).Limited precision of Quantity Limit, Delta Limit and Vega Limit to 4 decimals.
Release 07.10.2025
JSON-RPC API changes
The following API updates will be included in this release:Breaking Changes:
Release 02.09.2025
JSON-RPC API changes
The following API updates will be included in this release:Non-Breaking Changes:USDC rewards in APIAdded USDC APR data to public/get_currencies and public/get_apr_history.Check reward eligibilityIntroduced new method private/get_reward_eligibility returning reward eligibility status and 7-day SMA APR per currency.
Release 05.08.2025
JSON-RPC API changes
The following API updates will be included in this release:Breaking ChangesRestriction on Viewing API Key SecretsAPI keys with the account:read scope can no longer view secrets of other API keys, even if those keys share the same scope.Only API keys with the account:read_write scope are now permitted to view API key secrets.Non-Breaking ChangesInformation regarding all allowed linear option combosThe public/get_index_price_names method now provides information regarding the potential creation of future/option combinations for the specified index.Block Trade expiration is returned in the APIAdded expires_at to private/verify_block_trade response.
Release 01.07.2025
JSON-RPC API changes
The following API updates will be included in this release:Non-Breaking ChangesThe currency parameter is now optional for the private/get_block_trades method. If the method is called without specifying a currency, it will return block trades for all available currencies.
Release 10.06.2025
JSON-RPC API changes
The following API updates will be included in this release:Breaking ChangesDeprecated the max_show parameter and introduced display_amount to define the visible portion of an iceberg order.The private/buy, private/sell, and private/edit API methods now support the optional display_amount parameter.Order responses and events for iceberg orders now include display_amount (current visible portion) and refresh_amount (initially requested display amount).
refresh_amount remains constant throughout the order’s lifecycle. It represents the intended size of each iceberg “tip” as it gets replenished. The actual display_amount can be **lower than **refresh_amount when the order is partially or nearly fully filled.For example, if the total order amount is 10,000, refresh_amount is 1,000, and 9,500 has already been filled, the current display_amount would be 500 — the remaining visible portion.
Fee discounts are now returned per currency pair in the responses of private/get_account_summary and private/get_account_summaries.Rate limiting for public/get_instruments on websocket API has been updated: 1 request per 10 seconds, with a burst of 5.
To avoid rate limits, we recommend using either the **REST requests **or the WebSocket subscription to instrument_state.{kind}.{currency} for real-time updates.
Added a new field beneficiary_vasp_website to private/add_to_address_book, private/update_in_address_book, and private/get_address_book. This field is mandatory if the address belongs to a VASP not listed among known VASPs.Non-Breaking ChangesAdded a new extra_currencies parameter to the private/add_to_address_book method, allowing a list of valid ERC20 currencies. The extra_currencies parameter can only be used when currency is set to an ERC20 and type is set to withdrawal.Introduced a new event channel: block_trade_confirmations.{currency}, which functions like block_trade_confirmations but supports filtering by currency for more efficient data handling.FIXBreaking changesAs part of the iceberg order feature rollout, the FIX API now uses DisplayQty(1138) tag instead of MaxShow(210). Additionally the RefreshQty(1088) tag has been added as a non-mandatory field in Execution Reports (8). This optional tag defines the quantity used to refresh DisplayQty.
Release 13.05.2025
JSON-RPC API changes
The following API updates will be included in this release:Breaking ChangesThe public/exchange_token method now supports an optional scope parameter. This allows overriding the token scope when creating a new session for a subaccount. Scopes cannot be elevated beyond the caller’s permissions. If no session scope is provided to public/exchange_token then the provided refresh_token (and corresponding access_token) will be invalidated.
Important (Breaking Change)In the previous version, the scope parameter wasn’t available. As of this release, if no scope is provided, the associated refresh_token and access_token will be invalidated. When the scope parameter is provided to public/exchange_token, the created token will no longer include the mainaccount scope.This affects all implementation relying on the previous  behaviour and may lead to unexpected session terminations if not updated accordingly.We recommend explicitly providing a session scope, along with any other required scopes, to both public/auth and public/exchange_token.More details about access scopes can be found in our API documentation.
The methods private/get_portfolio_margins and public/get_portfolio_margins have now been fully removed from the API, following a period of deprecation.
Please head to private/simulate_portfolio to perform simulation on current margin models.
Non-Breaking ChangesWe have introduced a new public/get_apr_history method. This method retrieves historical APR data for specified currency. This applies to yield-generating tokens, currently including USDE and STETH.The apr field has been added to the /public/get_currencies result. It represents the Simple Moving Average (SMA) of the last 7 days of rewards. If there are fewer than 7 days of reward data, the APR is calculated as the average of the available rewards. This applies to yield-generating tokens, currently including USDE and STETH
Release 15.04.2025
JSON-RPC API changes
The following API updates will be included in this release:
  • An ip field has been added to trade type transaction logs in private/get_transaction_log.
  • Added price parameter to /private/add_block_rfq_quote and /private/edit_block_rfq_quote. This parameter can be used as aggregated price for quoting future spreads.
  • Added new endpoint /private/get_mmp_status to retrieve MMP status for a triggered index or MMP group.
Release 01.04.2025
JSON-RPC API changes
The following API updates will be included in this release:
  • The public/get_expirations endpoint now supports filtering by currency pair using the new currency_pair parameter.
  • The main account can now use the subaccount_id parameter in private/get_transaction_log to retrieve the transaction log for a specific subaccount
Release 04.02.2025
JSON-RPC API changes
Release 08.01.2025
JSON-RPC API changes
The following API updates have been added recently and are already available for use:
  • A new transaction type, options_settlement_summary, has been added to /private/get_transaction_log. This provides realized and unrealized profit and loss for an account’s option positions.
  • Deposit originator information can now be submitted using /private/set_clearance_originator (docs).
Release 30.10.2024
JSON-RPC API changes
There are no API changes.
Release 08.10.2024
JSON-RPC API changes
A new method public/get_expirations has been added. It returns a map of all expiration strings for the given currency and instrument kind.We added validation to check the tick size of secondary OTO, OCO, and OTOCO orders when they are placed, in addition to the existing validation when they are triggered. Affected methods:
  • private/buy
  • private/sell
Release 03.09.2024
JSON-RPC API changes
private/add_to_address_book and private/update_in_address_book: when executed for one of the ETH/ERC20 supported currencies, we will automatically add or update the address for all other ETH/ERC20 supported currencies.
Release 04.07.2023
JSON-RPC API changes
Allow main account to read the account summary, trades and positions of a subaccount. To do this use the subaccount_id parameter. Supported methods:
  • /api/v2/private/get_account_summary
  • /api/v2/private/get_user_trades_by_currency
  • /api/v2/private/get_positions
Release 22.02.2023
JSON-RPC API changes
/public/get_order_book, get_order_book_by_instrument_id:Random numbers for the depth parameter are no longer permitted. Supported depth levels are [1, 5, 10, 20, 50, 100, 1000, 10000]. If the depth parameter is not one of the supported levels it will be rounded up to the closest supported level, with a maximum value of 10,000.private/toggle_portfolio_margining:The user_id parameter is now optional (by default the authenticated user will be used). The method is also available for subaccounts. This means that as of now users that only have access to one of the sub-accounts can also switch margin settings from standard to portfolio margining (and vice versa).
Release 26.03.2020
JSON-RPC API changes
For API v2 a price_change response/notification parameter has been introduced, it reflects 24-hour asset price change.API v2 request of private/get_account_summary has been extended with a field of ‘creation_timestamp’.When the “tail” switch is on, the API console will automatically select the newest notification response.