Skip to main content
A Member is the Starbase trading participant. You cannot create a Starbase API key, authenticate to a gateway, or receive a rate-limit allocation until the target account belongs to an active Member. Do this before Creating a Starbase API Key. Skipping this step is the usual cause of the “No active member” error, and leaves the subaccount with no Starbase authentication.
Members are configured on the main account only. Subaccounts cannot create or manage Members. Switch into the main-account UID in the Account Panel (or authenticate as the main account over the classic JSON-RPC API) before you continue.
The Starbase section is only visible after your account has been authorized by a Deribit admin. If you do not see the section, contact your Account Manager or support@deribit.com.
A Member groups one or more portfolios (main account and/or subaccounts) into a single trading participant. See Account Model for the concepts, rate-limit sharing, and margin-mode constraints.

​
Who must belong to a Member

Add every main-account or subaccount UID that will trade on Starbase. A subaccount left outside every Member continues to use the standard Deribit APIs only — it has no way to authenticate to Starbase.
Most clients can configure only one Member. Add every UID that needs Starbase access to that Member. Broker clients that require separate Members for independent end clients must contact support@deribit.com to have multi-Member access enabled. The panel may display an option to add another Member even when the account is not enabled to save it.

​
Front-end interface

1

Switch to the main account

Open the Starbase section of the Account Panel while logged in as the main account. The Starbase section is separate from the standard API section.Starbase Section
2

Add a Member

Click Add Member and fill in:
  • Member Name: a label for this Member (for example Primary)
  • Accounts: select every main-account and/or subaccount UID that should trade on Starbase Starbase Members List
Click Add Member to open the dialog:Add Member DialogOnce saved, the Member appears in the Starbase member list.
3

Assign any remaining subaccounts

If a subaccount was created after the Member, or was omitted from the first save, edit the Member and add its UID. API key creation is scoped to the Member that the current account belongs to — assigning the account later is what unblocks key creation for that UID.
“No active member” error: Key creation fails if the target account does not belong to an active Member. Add the account to a Member first, then create the key while switched into the subaccount UID that will use it.

​
Create and assign a Member via API

Authorized main accounts can manage Members with the classic JSON-RPC API. Creating, updating, or deleting a Member requires account:read_write, main-account authentication, and Direct Access trading to be enabled. Listing Members requires account:read. Omit member_id to create a Member. accounts must be a non-empty list of UIDs:
To assign additional UIDs later, send the existing member_id with the full replacement accounts list — omitting accounts on an edit clears the Member’s accounts:
Confirm the result with private/get_members. See also private/set_member and private/delete_member.
Toggling is_active cannot be combined with a name or accounts change in the same request. A pure active-state toggle must resend the Member’s current name and accounts. A Member cannot be created inactive.

​
Next steps

Creating a Starbase API Key

Create keys on each assigned subaccount after the Member exists

Account Model

How Members, portfolios, rate limits, and margin modes relate

Connectivity Quickstart

Continue from Member setup through gateway validation

Production Readiness Checklist

Confirm Member assignment before the order-entry go-live