> ## 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.

# Creating a Starbase API Key

> Create Starbase API keys, pick Starbase-specific scopes, and resolve the No active member error after the target account belongs to a Member.

Starbase API keys are created through the [**Starbase section**](https://www.deribit.com/account/BTC/starbase/api-keys) of the Account Panel (not the API section). The creation flow is otherwise the same as standard Deribit API keys, but with a different set of available scopes.

<Card title="Create and assign a Member first" icon="users" href="/starbase/creating-member">
  Complete [Creating and Assigning a Member](/starbase/creating-member) on the main account before generating any key. Key creation is scoped to a Member; skipping that step is the usual cause of the **"No active member"** error.
</Card>

<Warning>
  The Starbase section is only visible after your account has been authorized by a Deribit admin. If you do not see the section, contact <a href="mailto:support@deribit.com" style={{ whiteSpace: "nowrap" }}>[support@deribit.com](mailto:support@deribit.com)</a>.
</Warning>

<Note>
  **"No active member" error**: If key creation fails with a "No active member" error, the account you are creating the key for does not belong to an active Member. Go back to [Creating and Assigning a Member](/starbase/creating-member), add the account on the **main-account** level, then create the key while switched into the subaccount UID that will use it.
</Note>

<Note>
  Starbase API key management is a sensitive operation. If your account has Two-Factor Authentication (2FA) enabled, you will be prompted for a security key confirmation. See [Security Keys](/articles/security-keys) for details.
</Note>

## Front-end interface

<Steps>
  <Step title="Navigate to the Starbase Section">
    Open the [**Starbase section**](https://www.deribit.com/account/BTC/starbase/api-keys) in the Account Panel.

    The Starbase section is separate from the standard **API** section. Make sure you are in the correct section.

    <img src="https://mintcdn.com/deribit/tO0Fri3Xhug1I2Vk/starbase/starbase_tab.png?fit=max&auto=format&n=tO0Fri3Xhug1I2Vk&q=85&s=e3a4acdcc5ef7947f66e36ab782074fb" alt="Starbase Section" width="568" height="1154" data-path="starbase/starbase_tab.png" />

    Switch into the **subaccount UID** that will use the key. The Member must already include this UID. See [Creating and Assigning a Member](/starbase/creating-member) if it does not.
  </Step>

  <Step title="Create a New API Key">
    With the Member selected, press **Add new key** to open the key creation dialog.

    Provide an optional **Name** for the key, then select one or more scopes from the following:

    | Scope | Description |
    | - | - |
    | **FIX Drop Copy** | Receive a consolidated drop copy of all activity on the portfolio via the [FIX Drop Copy API](/starbase/fix-drop-copy-api) |
    | **SBE Order Entry** | Submit, amend, and cancel orders via the [Simple Binary Encoding (SBE) Order Entry API](/starbase/binary-api-reference) |
    | **REST** | Access REST endpoints (portfolio management, cancel all, etc.) |

    <Note>
      Scopes are not currently enforced on the REST gateway: any Starbase API key belonging to a direct-access-enabled portfolio can call every Starbase REST endpoint (order entry and portfolio management, including `cancel_all`, `lock_portfolio`, and `unlock_portfolio`), regardless of the scopes selected here. Scope-based restrictions may be introduced in the future, so select the scopes that match the key's intended use.
    </Note>

    <Note>
      Multicast market data and the retransmit API are unauthenticated. No API key or scope is required to subscribe to them.
    </Note>

    <img src="https://mintcdn.com/deribit/tO0Fri3Xhug1I2Vk/starbase/starbase_api_key.png?fit=max&auto=format&n=tO0Fri3Xhug1I2Vk&q=85&s=dfbc42e906239bfff26854c18b765dca" alt="Create API Key Dialog" width="1838" height="792" data-path="starbase/starbase_api_key.png" />

    Click **Create API Key** to generate the key.
  </Step>

  <Step title="Save Your Credentials">
    Once created, you will receive a **Client ID** and **Client Secret**.

    <img src="https://mintcdn.com/deribit/tO0Fri3Xhug1I2Vk/starbase/starbase_credidentials.png?fit=max&auto=format&n=tO0Fri3Xhug1I2Vk&q=85&s=2f3a88aefd47c68224fe3ce331270680" alt="API Key Created" width="1812" height="450" data-path="starbase/starbase_credidentials.png" />

    <Warning>
      The Client Secret is only shown once when the key is created. Store it securely, as you cannot retrieve it later.
    </Warning>

    For a description of what these credentials are, see the [Client ID and Client Secret](/articles/creating-api-key#client-id) section of the Creating new API key guide.
  </Step>
</Steps>

## API key limits

Each subaccount can have up to **8 Starbase API keys**. Because each gateway connection requires its own API key, plan your key allocation based on the number of gateway connections you intend to maintain.

Each API key can hold **one connection per gateway**. With 5 gateway pairs, that is up to 10 simultaneous connections per key. Reconnecting the same key to the same gateway terminates the existing session. See [Gateway Connectivity](/starbase/gateway-connectivity#api-keys) for the full connection rules.

Starbase API keys use a separate counter from standard Deribit API keys. Starbase API keys do not count toward your standard API key quota, and standard API keys do not count toward your Starbase quota. A standard Deribit API key cannot authenticate to Starbase. You always need a separate Starbase key.

## Next steps

<CardGroup cols={2}>
  <Card title="Creating and Assigning a Member" icon="users" href="/starbase/creating-member">
    Required before any Starbase API key can be created
  </Card>

  <Card title="Gateway Connectivity" icon="server" href="/starbase/gateway-connectivity">
    How API keys map to gateway connections and connection rules
  </Card>

  <Card title="Binary API Reference" icon="code" href="/starbase/binary-api-reference">
    SBE protocol structure, message headers, and data types
  </Card>

  <Card title="Placing a New Order" icon="arrow-up-right" href="/starbase/placing-new-order">
    Submit your first order via the SBE Order Entry API
  </Card>

  <Card title="FIX Drop Copy API" icon="copy" href="/starbase/fix-drop-copy-api">
    Consolidated drop copy of all portfolio activity
  </Card>

  <Card title="Session Messages" icon="plug" href="/starbase/session-messages">
    Logon, logout, and heartbeat session message flows
  </Card>

  <Card title="Cancel on Disconnect" icon="link-slash" href="/starbase/cancel-on-disconnect">
    Automatic order cancellation on connection loss
  </Card>
</CardGroup>


## Related topics

- [Creating and Assigning a Member](/starbase/creating-member.md)
- [Starbase Connectivity Quickstart](/starbase/quickstart.md)
- [Infrastructure, Connectivity & Best Practices](/starbase/connectivity-best-practices.md)
- [REST Order Gateway Authentication](/starbase/rest-authentication.md)
- [Portfolio Management](/starbase/portfolio-management.md)