> ## Documentation Index > Fetch the complete documentation index at: https://docs.deribit.com/llms.txt > Use this file to discover all available pages before exploring further. # Spot Trading Routed to Coinbase Exchange > Identify Deribit spot instruments routed to Coinbase Exchange and see which order entry and market data features differ on the JSON-RPC and FIX APIs. Selected spot instruments are matched on Coinbase Exchange (CBE) rather than on the Deribit matching engine. You trade them through the usual Deribit APIs, with the same authentication, the same sessions and the same instrument names, but several features behave differently or are unavailable. Derivatives are never affected, including derivatives on the same currency pair. A routed spot instrument does not change anything about the futures, perpetuals or options quoted in the same currencies. This article covers both the JSON-RPC and WebSocket API and the FIX API. Where the two differ only in spelling, the rule is stated once and the FIX tag values are given alongside it. ## Identifying routed instruments [`public/get_instrument`](/api-reference/market-data/public-get_instrument) and [`public/get_instruments`](/api-reference/market-data/public-get_instruments) return `is_cbe_routed: true`, and its alias `is_csr: true`, for routed spot instruments: ```json theme={null} { "instrument_name": "USDC_USDT", "kind": "spot", "is_cbe_routed": true, "is_csr": true, "...": "..." } ``` Both fields are omitted entirely for every other instrument, so test for their presence rather than for a `false` value. Routed spot instruments also omit `block_trade_commission`, `block_trade_tick_size` and `block_trade_min_trade_amount`, because block trading is not available on them. Which pairs are routed is a configuration decision that can change, so read the flag from the instrument metadata instead of maintaining your own list. The [`instrument.creation.{kind}.{currency}`](/subscriptions/market-data/instrumentcreationkindcurrency) and [`instrument.state.{kind}.{currency}`](/subscriptions/market-data/instrumentstatekindcurrency) notifications carry `is_csr` only; the `is_cbe_routed` alias is added by the two instrument methods above. On FIX there is no routing flag in the reference data. [`Security List`(`y`)](/fix-api/production/security-list) returns routed instruments as ordinary `FXSPOT` entries, so identify them through the JSON-RPC methods above. ## Order entry ### JSON-RPC The restrictions below apply to [`private/buy`](/api-reference/trading/private-buy), [`private/sell`](/api-reference/trading/private-sell), [`private/edit`](/api-reference/trading/private-edit) and [`private/edit_by_label`](/api-reference/trading/private-edit_by_label). | Feature | Routed spot | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | `type` | `limit`, `market` and `stop_limit` only. `market_limit` and every other advanced or trigger type is rejected | | `time_in_force` | `good_til_cancelled`, `immediate_or_cancel` and `fill_or_kill` on limit orders. On market orders, either omit it or send `immediate_or_cancel` | | `post_only` | Allowed only together with `reject_post_only: true` | | `reduce_only` | Not supported | | `display_amount` (iceberg) | Not supported | | `trigger` on stop-limit orders | `last_price` only | | `mmp` | Not supported | | Linked orders (OTO, OCO, OTOCO) | Not supported | | Block trades and Block RFQ legs | Not supported | Cancelling works normally. [`private/cancel`](/api-reference/trading/private-cancel), [`private/cancel_all_by_instrument`](/api-reference/trading/private-cancel_all_by_instrument) and the other cancel methods accept routed spot orders, including untriggered stop-limit orders. ### FIX The same restrictions apply to [`New Order Single`(`D`)](/fix-api/production/new-order-single) and [`Order Cancel/Replace Request`(`G`)](/fix-api/production/order-cancel-replace). | Tag | Name | Accepted on routed spot | | ---- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | 40 | `OrdType` | `1` = Market, `2` = Limit and `4` = Stop Limit only | | 59 | `TimeInForce` | `1` = Good 'Til Cancelled, `3` = Immediate or Cancel and `4` = Fill or Kill. `0` = Good 'Til Day is rejected on every spot instrument, routed or not | | 18 | `ExecInst` | `6A` only. A bare `6` is rejected with `post_only_not_allowed`, and `E` (reduce only) with `reduce_only_not_allowed` | | 1138 | `DisplayQty` | Not supported. Iceberg orders are rejected with `iceberg_not_allowed` | | 5127 | `DeribitConditionTriggerMethod` | Required on stop limit orders, and must be `2` = trade | ### Post-only Unlike native Deribit post-only, the price of a routed post-only order is never adjusted into the spread. The order is either placed unmodified or rejected, which is why `reject_post_only: true` — `ExecInst`(`18`)=`6A` on FIX — is mandatory whenever post-only is requested. A post-only order without it is rejected with `post_only_not_allowed` (11055). If the order would match on arrival, it is rejected with `post_only_reject` (11054), the same as on the native matching engine. ### Restrictions shared with all spot instruments Some of the limitations above are not specific to routing and apply to every spot instrument, routed or not. `good_til_day` is rejected for all spot orders, as are `reduce_only` and `mmp`. On JSON-RPC these come back as `Invalid params` (-32602) rather than as a routing-specific error code. ### Errors and rejections On JSON-RPC the error is returned in the response to the request. On FIX, rejected orders arrive as an [`Execution Report`(`8`)](/fix-api/production/execution-reports) with `OrdStatus`(`39`)=`8` and the reason in `Text`(`58`). | Code | Message | Cause | | ----- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | 11030 | `other_reject ` | The rejection originated at Coinbase, for example `other_reject price_band` or `other_reject not_enough_funds` | | 11054 | `post_only_reject` | A post-only order would have matched on arrival | | 11055 | `post_only_not_allowed` | Post-only was requested without the reject flag | | 11059 | `iceberg_not_allowed` | `display_amount`, or `DisplayQty`(`1138`), was set on a routed spot instrument | | 11060 | `not_supported_for_coinbase_routed_spot` | The requested order type, time in force, trigger, block trade or market data call is not available on a routed spot instrument | | 13922 | `linked_order_type_not_supported_for_csr_spot` | A linked order (OTO, OCO or OTOCO) was submitted for a routed spot instrument | | | `reduce_only_not_allowed` | `ExecInst`(`18`)=`E` was sent for a routed spot instrument | See [Error codes](/articles/errors) for the full list. Code 11060 is also returned under its legacy message `not_supported_for_csr_spot`; treat the two as equivalent. Fills are asynchronous. `private/buy`, `private/sell`, `private/edit` and `private/edit_by_label` — and, on FIX, the first `Execution Report` for the order — acknowledge the order once Coinbase has accepted it, and do not necessarily carry any fills. Subscribe to [`user.trades.{instrument_name}.{interval}`](/subscriptions/user/usertradesinstrument_nameinterval) and [`user.orders.{instrument_name}.{interval}`](/subscriptions/user/userordersinstrument_nameinterval), or track the subsequent Execution Reports on the FIX session, to follow execution. ## Market data Deribit only observes a match on Coinbase when one of your own orders was a party to it, so the public trade tape it could publish for a routed instrument would be incomplete. Rather than serve partial data, trade-derived methods, channels and message types are rejected. Your own fills are always complete: [`private/get_user_trades_by_instrument`](/api-reference/trading/private-get_user_trades_by_instrument), the `user.trades.*` channels, and on FIX both [Execution Reports](/fix-api/production/execution-reports) and [`Trade Capture Report`(`AE`)](/fix-api/production/trade-capture-report), report every trade you were a party to. ### Methods that return an error These return `not_supported_for_coinbase_routed_spot` (11060): * [`public/get_last_trades_by_instrument`](/api-reference/market-data/public-get_last_trades_by_instrument) * [`public/get_last_trades_by_instrument_and_time`](/api-reference/market-data/public-get_last_trades_by_instrument_and_time) * [`public/get_last_trades_by_currency`](/api-reference/market-data/public-get_last_trades_by_currency) and [`public/get_last_trades_by_currency_and_time`](/api-reference/market-data/public-get_last_trades_by_currency_and_time), when `kind` is `spot` or `any` — `any` is the default when `kind` is omitted, and a currency counts as routed when it is either the base or the quote of a routed pair * [`public/get_tradingview_chart_data`](/api-reference/market-data/public-get_tradingview_chart_data) Requesting a derivative `kind` on a currency that happens to have a routed spot pair is unaffected, so `kind: "future"` still returns trades for that currency. ### Subscriptions that are rejected [`public/subscribe`](/api-reference/subscription-management/public-subscribe) refuses these channels for routed instruments, reporting them as invalid channels rather than as error 11060: * [`trades.{instrument_name}.{interval}`](/subscriptions/trades/tradesinstrument_nameinterval) * [`trades.{kind}.{currency}.{interval}`](/subscriptions/trades/tradeskindcurrencyinterval) for `kind` `spot` or `any` * [`chart.trades.{instrument_name}.{resolution}`](/subscriptions/market-data/charttradesinstrument_nameresolution) `currency: "any"` is rejected as well whenever any routed spot pair exists, so subscribe per currency, or per instrument, if you need spot trades for non-routed pairs. ### FIX market data * `MDEntryType`(`269`)=`2` (Trade) is rejected for routed spot instruments in a [`Market Data Request`(`V`)](/fix-api/production/market-data-request), which is answered with a [`Market Data Request Reject`(`Y`)](/fix-api/production/market-data-request-reject). `0` (Bid) and `1` (Offer) requested in the same message are still served. * [`Market Data Snapshot/Full Refresh`(`W`)](/fix-api/production/market-data-snapshot) and [`Market Data Incremental Refresh`(`X`)](/fix-api/production/market-data-incremental) therefore never carry trade entries for routed spot instruments. Bid and offer snapshots and incremental updates are fed from the full Coinbase L2 book, and [`Security List Request`(`x`)](/fix-api/production/security-list-request) and [`Security Status Request`(`e`)](/fix-api/production/security-status-request) are unaffected. ### Responses that omit fields Two responses drop fields instead of returning an error: * [`public/get_trade_volumes`](/api-reference/market-data/public-get_trade_volumes) omits `spot_volume`, and `spot_volume_7d` and `spot_volume_30d` under `extended`, for any currency that has a routed pair. The futures and options volume fields are unaffected. * [`public/ticker`](/api-reference/market-data/public-ticker) and the [`ticker.{instrument_name}.{interval}`](/subscriptions/market-data/tickerinstrument_nameinterval) channel omit `volume_notional` and `volume_usd` from `stats` for routed spot. The base currency `volume` field is still returned. ### What is unaffected Order book data works normally, fed from the Coinbase book: [`public/get_order_book`](/api-reference/market-data/public-get_order_book), [`public/get_order_book_by_instrument_id`](/api-reference/market-data/public-get_order_book_by_instrument_id), [`public/get_book_summary_by_currency`](/api-reference/market-data/public-get_book_summary_by_currency) and [`public/get_book_summary_by_instrument`](/api-reference/market-data/public-get_book_summary_by_instrument), together with the [`book.*`](/subscriptions/orderbook/bookinstrument_nameinterval), [`quote.*`](/subscriptions/market-data/quoteinstrument_name) and [`ticker.*`](/subscriptions/market-data/tickerinstrument_nameinterval) channels. ### Getting the data from Coinbase For the full public trade tape, candles and venue volume, query Coinbase Exchange directly: * [Get product trades](https://docs.cdp.coinbase.com/exchange/reference/exchangerestapi_getproducttrades) * [Get product candles](https://docs.cdp.coinbase.com/exchange/reference/exchangerestapi_getproductcandles) * [Get all product volume](https://docs.cdp.coinbase.com/exchange/reference/exchangerestapi_getproductvolume) * The [`matches` WebSocket channel](https://docs.cdp.coinbase.com/exchange/websocket-feed/channels) and the [FIX Market Data API](https://docs.cdp.coinbase.com/exchange/fix-api/market-data) ## Related topics - [private/edit_by_label](/api-reference/trading/private-edit_by_label.md) - [private/edit](/api-reference/trading/private-edit.md) - [private/buy](/api-reference/trading/private-buy.md) - [private/sell](/api-reference/trading/private-sell.md) - [Deribit Production FIX API Overview](/fix-api/production/overview.md)