Skip to main content
The Starbase direct access (SBE order entry) gateways go live on Tuesday, 11 August 2026, immediately after the scheduled maintenance at 9:00 AM UTC. The maintenance is followed by a longer cancel-only period, during which the order entry gateways are fully available.
This checklist is for clients already onboarded to Starbase. Work through the steps below to make sure your transition to production order entry is smooth.
Read the Connectivity Quickstart first — it covers network access, key creation, and end-to-end validation. This checklist assumes that setup is done and only verifies the points most likely to block a smooth go-live.
1

Confirm Your Member Setup

A Member groups the portfolios (accounts/subaccounts) that trade on Starbase. Members are managed at the main-account level only — subaccounts cannot create or manage Members.
  • Add every main-account or subaccount UID that needs Starbase access to your Member. Most clients can configure exactly one Member. Broker clients that require separate Members for independent end clients must contact support@deribit.com to have multi-Member access enabled.
  • Verify the setup in the Starbase section of the Account Panel or programmatically with private/get_members.
A subaccount that does not belong to an active Member cannot authenticate to Starbase — API key creation for it fails with a “No active member” error.
See Account Model and Creating a Starbase API Key for details.
2

Check API Key Scopes for SBE Order Entry

Starbase API keys are separate from standard Deribit API keys — a standard key cannot authenticate to Starbase.
  • Create keys in the Starbase section of the Account Panel while switched into the subaccount UID that will use the key.
  • The key needs the SBE Order Entry scope to submit, amend, and cancel orders. Add FIX Drop Copy and REST scopes if your integration uses those APIs.
  • Plan your key allocation: up to 8 Starbase API keys per subaccount, one connection per gateway per key. Reconnecting the same key to the same gateway terminates the existing session.
3

Configure MMP and Use the Risk Bypass

The lowest-latency order entry path on Starbase is the MMP risk bypass: MMP-tagged flow goes straight from the gateway to the matching engine, skipping the risk module. It also reduces load on Deribit’s risk and margin engines and is unaffected by the ongoing pre-trade risk testing.
  • Orders — set the MMP flag (field 10, bit 4) on NewOrderRequest. The bypass applies to both making and taking flow.
  • Mass quotes — MMP is always enforced through the mmpGroupId referenced on every MassQuoteRequest, so mass quoting uses the bypass by default.
  • Configure your MMP limits (quantity, delta, vega, interval, frozen time, and Max Quote Quantity) with private/set_mmp_config before go-live. Note the scoping difference: order MMP applies per subaccount and base/quote pair, while mass-quote MMP works through an explicit mmpGroupId.
See Market Maker Protection for configuration, reset, and monitoring details.
4

Update to the Latest SBE XMLs

Download the current integration resources and regenerate your SBE codecs (or update to the latest SDK):
As of 9 August 2026, the latest schema versions are: order entry schema version 12 (semanticVersion 1.4) and market data schema version 1 (semanticVersion 1.0). The version and semanticVersion attributes are at the top of each XML file — check them against your local copies.
Note that reference data is published on the multicast market data feeds, and your integration should be comfortable consuming it from there:
  • InstrumentDefinition — full instrument definitions on the snapshot channels
  • IndexInfo (12) — index price per currency pair
  • InstrumentInfo (14) — minSellPrice, maxBuyPrice, and markPrice per instrument
  • InstrumentRef (15) — funding, settlement/delivery prices, and open interest per instrument
See Reference Data for full message details.
5

Test Order Entry Logon and Heartbeats

The session-level endpoints (Logon, Logout, Heartbeat, and Test) are already enabled on the production gateways for connectivity testing. If you have not tested order entry logon yet, do so as soon as possible.
  1. Establish TCP connectivity to the gateway pair for each product group you trade — see Gateway Connectivity.
  2. Send a LogonRequest and expect a LogonResponse — note the heartbeatIntervalSeconds value the server returns.
  3. Keep the session alive with Heartbeat messages at the expected interval, and use TestRequest to elicit a Heartbeat echoing your correlationId.
  4. Repeat on both the A and B sides of each required gateway pair.
Do not treat a successful TCP connection as a pass — authentication and the heartbeat exchange must both work. See Session Messages for the full message flows.
6

Know Where to Find Fees, Open Orders, and Order History

Starbase order state is distributed differently from the standard Deribit APIs. Before go-live, make sure your reconciliation and reporting pull each data type from the right place:
If you need to adjust your Member setup quickly around go-live, private/set_member, private/delete_member, and private/get_members are available on the standard JSON-RPC API and in the Starbase tab of the Account Panel.

​
Questions?

If anything on this list is not working as expected:

​
Next steps

Infrastructure & Best Practices

Deployment costs, gateway architecture, failover, and protocol selection.

Gateway Connectivity

Production and test addresses, ports, and gateway pairs.

Risk Bypass

How MMP-tagged flow bypasses the risk module.

Starbase Changelog

Release notes and go-live announcements.

Related topics

Starbase API ChangelogStarbase Connectivity QuickstartStarbase API OverviewInfrastructure, Connectivity & Best PracticesOptions Data Collection