1. Deribit Support
  2. Support
  3. Technical Information

Connection Management

  • Updated

Connection

A connection is a single, continuous link between a client and a server over a network. Users can authenticate with the connection scope as these connections are exempt from the session limit. It is also set and used automatically by the server when neither connection nor session scope is provided within the request.

Connection scope

  • Access and refresh tokens are strictly tied to the specific connection in which they were granted.

  • Tokens are valid only during the active connection. Once the connection is terminated, the tokens become invalid, requiring a new authentication process for a new connection.

  • A maximum of 32 connections per IP address is permitted. If a 33rd connection attempt is made, it will not be successful.

Session

A session extends beyond a single connection and represents a period of interaction between a user and a server, potentially across multiple connections. Users can authenticate with the session:name scope to bind their connection with a named session.

Session scope

  • Tokens issued can be used across different connections, beneficial when a user’s connection might be intermittently interrupted.

  • Tokens are tied to the session, not to any specific connection, allowing users to reconnect using the same tokens until the session expires.

  • This scope is ideal for environments where users switch between devices or network connections, as it does not require repeated authentication.

  • When using WebSocket it also allows skipping providing access_token with every subsequent request.

  • Re-authenticating with a refresh token under session scope does not add new sessions but refreshes the existing one.

  • A maximum of 16 sessions per UID is allowed. When session 17 is opened the Deribit removes the one that was not refreshed in the longest time.

Connection Lifetime

Each established HTTP connection has an expiration timer of 15 minutes. Users wishing to maintain an HTTP connection beyond this period should utilize signature authorization for continued access without impacting session limits.

Cancel on disconnect

The Cancel on Disconnect (COD) feature in the API supports two types of scope settings: connection and account. Please note cancel on disconnect is not supported via HTTP.

  • Connection Scope: When COD is set with the scope as connection, it applies only to the specific connection through which it is set. This setting does not affect any other existing or future connections. Each connection must individually enable COD if required.

  • Account Scope: Setting the COD scope to account extends the feature to the initial connection where it is set and automatically applies it to all subsequent connections made under the same account. This ensures that COD is enabled by default for new connections without the need to set it individually for each one.

FIX implementation

Upon initiating a session with the Logon (A) message, users have the option to enable or disable Cancel on Disconnect for that session using Tag 9001. Later, when logging out, they can override this setting with Tag 9003.

Message Types

  • Logon (A): Initiates the session. Must be the first message sent by the client.

  • LogOut (5): Used by either party to terminate the session. The sender must wait for an echo before closing the socket.

Tags

  • Tag 9001 - CancelOnDisconnect: Boolean flag that controls session-level COD. Default is false (N). If not specified, the account’s default setting is used.

  • Tag 9003 - DontCancelOnDisconnect: If set to Y, disables COD for the connection despite previous settings at logon or account level. Default is false (N).