private/get_open_orders* methods and private order subscriptions do not return open Starbase orders or their lifecycle updates. Use an SBE order-entry session, the Starbase REST order snapshot, or FIX Drop Copy for Starbase order state. The Starbase REST gateway also provides utility endpoints such as portfolio-wide cancellation.
Two versions of the API documentation are available. You can switch between them using the version selector button at the top of the page. Changes in the upcoming version will be available in the production version after the next release. For release notes and information about upcoming releases, see the Starbase Changelog.
Starbase Changelog
Review dated schema releases, gateway changes, rollout announcements, and compatibility notes before upgrading or deploying to production.
Starbase is accessible exclusively through hosted colocation or a cross-connect in LD4, or through AWS Private Link for clients connecting from AWS infrastructure. Internet connectivity is not supported. Contact colo-support@coinbase.com to arrange access.
Binary Order Entry API
The Binary Order Entry API provides direct access to the matching engine using a high-performance binary protocol optimized for ultra-low latency trading.
- Order Entry: Place, amend, and cancel orders with minimal latency. Supports single orders, mass quotes (up to 15 double-sided quotes), and mass cancellation.
- Market Maker Protection (MMP): Built-in protection against adverse selection. See Market Maker Protection for details.
- Self Match Prevention (SMP): A highly flexible system to avoid matching orders internally.
Multicast Market Data
Market data is distributed via multicast channels organized by product type (BTC perpetuals/futures, BTC options, ETH perpetuals/futures, ETH options, etc.). The multicast channels have:
- Market-by-order data: Market data is sent as L3 data, allowing for full reconstruction of the order book.
- A/B Redundancy: Duplicate feeds (A and B) for high availability.
- Snapshot and Incremental Updates: Snapshot feeds provide the full order book state, while incremental feeds provide real-time updates.
FIX Drop Copy
The FIX Drop Copy feed provides a consolidated view of all orders and trades across an entire account, regardless of which gateway they were submitted through.
- Full order visibility: Captures all order lifecycle events — new, amended, filled, and cancelled.
- FIX 5.0 SP2: Standard FIX protocol for easy integration with existing OMS/EMS systems.
- Account-wide scope: Unlike per-gateway SBE connections, a single Drop Copy session covers the full portfolio.
Gateway Connectivity
Starbase gateways run in hot-hot A/B pairs for resilience, with independent rate limits on each side. Clients are expected to connect to both gateways in a pair simultaneously for optimal throughput and redundancy.
- Colocated cross-connect: Lowest latency option for clients physically present in Deribit’s data center.
- AWS Private Link: Secure private connectivity for clients on AWS without routing traffic over the public internet.
- Multiple gateway pairs: Gateways are partitioned by underlying asset (BTC, ETH, Tier 2/3) to allow horizontal scaling.
Scope and migration
- No spot trading on Starbase. Spot order books are not available on Starbase; spot trading will migrate to a brokered solution via Coinbase Exchange (CBE). Existing spot APIs remain unchanged in the meantime — see the spot announcement for details.
- Standard APIs are not going away. The standard WebSocket API will be supported indefinitely. The legacy SBE feed is scheduled for deprecation at the end of 2026. One exception: portfolios added to a Member can no longer use the legacy mass quotes API and must quote through the Starbase Binary API — all other standard API access, including regular order entry, is unaffected.
Integration resources
Connectivity Quickstart
Validate network access, sessions, market data, recovery, and production readiness.
Reference Data
Identify the authoritative source for instrument units, tick sizes, tiers, and other metadata.