Deribit Spot

Panama

CoinGecko Trust 8/10·#43 rank·213 BTC vol 24h·Panama·Est. 2016

Deribit Spot verbinden

Melde dich an, um deine Börse zu verbinden und dein Portfolio automatisch zu tracken

Über Deribit Spot

Deribit is a leading cryptocurrency exchange, primarily focused on options and futures trading for Bitcoin and Ethereum, holding a dominant market share in these derivatives.

Editorial summary aggregated from CoinGecko and CoinMarketCap exchange profiles for Deribit Spot, an exchange operating since 2016.

Deribit Spot at a Glance

Key facts about Deribit Spot compiled from verified market data and CoinGecko's exchange registry. These metrics help you evaluate liquidity, regulatory footprint and operational maturity before connecting a portfolio.

Trust Score: 8/10; Rank #43
24h Volume (normalized): 239 BTC
Active markets: 16 pairs
Land: Panama
Operating since: 2016; 10 years
Trading incentives: Not offered
CCXT integration: Supported; deribit_spot

Handelszugang & Integration

Deribit Spot is wired into Mantapex through the CCXT integration layer, so importing balances and trade history into a read-only portfolio requires an API key and a secret that you generate inside your own Deribit Spot account. Because Mantapex never custodies your funds, the keys you create should be scoped to read access only — withdrawal, transfer and trading permissions are unnecessary for portfolio tracking and should remain disabled. The trust score and rank shown in the Quick Facts above are sourced from CoinGecko's exchange framework, which blends reported liquidity, web traffic patterns, regulatory posture and API health into a single signal — useful when comparing Deribit Spot to peer venues, but never a substitute for your own due diligence. The headquarters jurisdiction shown above determines the regulatory framework, KYC tier and product mix Deribit Spot can offer a given user, and that scope can change as licensing evolves. Verify eligibility and the local terms of service on the official site before opening an account. The operating history reflected above means there is a comparatively deep public trail of incidents, audits, fee schedules and product launches you can review when sizing Deribit Spot against newer venues.

CCXT-kompatibel API-Schlüssel erforderlich API-Secret erforderlich

Connection metadata is read directly from Mantapex's CCXT integration manifest — credential requirements reflect what Deribit Spot itself exposes to read-only API consumers and may evolve as the venue updates its API.

Getting Started with Deribit Spot

Required Credentials: API-Schlüssel Geheimer Schlüssel

Konto, Verwahrung & Sicherheit bei Deribit Spot

Deribit Spot operates as a custodial trading venue: when you fund an account, the deposited assets are held in wallets controlled by the exchange and credited to your balance as a book-entry until you withdraw them. That trade-off — convenience and order-book liquidity in exchange for counterparty risk — is the central design choice of every centralised exchange and is what makes platform-level security so important to evaluate. Deribit Spot has been running its custody and matching infrastructure since 2016, which gives it 10 years of operational track record for users to review when judging incident history, fund-recovery policy and any insurance or reserve-fund coverage.

Almost every major centralised exchange — including Deribit Spot — operates under some form of KYC ("Know Your Customer") and AML ("Anti-Money-Laundering") obligations imposed by the jurisdiction it serves. Deribit Spot is reported with its operating entity in Panama, so its baseline KYC programme follows that jurisdiction's rules — additional verification may still be requested for higher-tier withdrawal or fiat-on-ramp limits, and access to specific products can be restricted depending on where the user resides. Expect to provide a government-issued ID document and a recent proof-of-address at minimum; higher verification tiers may add liveness checks, source-of-funds questionnaires and accredited-investor confirmations.

Enable two-factor authentication on the Deribit Spot account itself before generating any API keys. The strongest options are hardware security keys (FIDO2 / WebAuthn devices such as YubiKey or Solo) where supported, followed by an authenticator app on a dedicated device (Aegis, Raivo, 1Password, Authy in offline-only mode, or Google Authenticator). SMS-based 2FA is widely available but is the weakest of the common methods because of SIM-swap risk — if Deribit Spot only offers SMS, treat the account as more exposed and consider keeping balances on the venue smaller than you otherwise would. The 2FA factor should be different from anything you use to sign in elsewhere, and the recovery phrase or backup codes belong in offline cold storage, not in the same password manager you use to log in.

Use Deribit Spot's withdrawal-address whitelist if the feature is available. Whitelists turn a stolen API key or hijacked session into a much smaller blast radius: even with full account access, an attacker cannot send funds to an address that wasn't pre-approved and cleared a cool-down window. Combine this with anti-phishing codes (a short string that the exchange embeds in every legitimate email), a separate email account that's not used for anything else, and notification alerts for new logins, withdrawal requests and API-key creation. The same hygiene applies whether you actively trade or simply hold a long-term balance on Deribit Spot — most exchange-related losses originate from compromised individual accounts rather than platform-wide breaches.

For the specific case of connecting Deribit Spot to Mantapex, the additional hardening layer is straightforward: generate a dedicated API key for read-only portfolio sync, label it clearly (for example "Mantapex read-only sync"), disable every permission except the minimum the exchange exposes for balance and trade-history queries, and store the secret in a password manager so you can rotate it on a schedule. If Deribit Spot supports IP whitelisting and you connect from a stable address, restrict the key to that address. If you ever stop using Mantapex — or any other third-party dashboard — revoke the key on the exchange side rather than just deleting it from the dashboard, because the credential continues to authenticate against Deribit Spot's API until Deribit Spot itself invalidates it.

Security guidance on this page is generic exchange hardening that applies to every centralised crypto venue. For Deribit Spot's exchange-specific policies — fund-segregation model, proof-of-reserves cadence, insurance coverage and incident-response history — the canonical references are Deribit Spot's own Help Centre and any audit reports or attestations the venue publishes directly.

API-Zugangsdaten für Deribit Spot

Connecting Deribit Spot as a read-only portfolio source on Mantapex relies on the credentials defined by Deribit Spot's own API. The matrix below mirrors exactly what the CCXT integration layer asks for — ticked rows mean the field is required to authenticate, untouched rows mean Deribit Spot doesn't ask for that field at all.

API-Schlüssel

Public identifier that pairs your read-only access with your exchange account.

API-Secret

Private signing string used to authenticate each request — never share it.

API-Passphrase

Additional passphrase set when the key is created (KuCoin, OKX-style models).

Konto-UID

Numeric account identifier that some venues require alongside the API key.

Unterkonto-ID

Used when the venue scopes API access to a specific sub-account.

Anmeldename

A separate username distinct from email, used by a small number of CCXT-supported venues.

TOTP-/2FA-Secret

Time-based one-time-password seed for endpoints that demand a fresh 2FA code.

Privater Wallet-Schlüssel

Self-custody signing key — required only by DEX / on-chain integrations.

Wallet-Adresse

On-chain address tied to the private key for DEX-style integrations.

Bearer-Token

OAuth-style bearer token, occasionally used in place of an HMAC API key pair.

In short, Deribit Spot requires 2 credentials to authenticate API requests: API-Schlüssel and API-Secret. All of these are generated from inside the exchange's own dashboard — Mantapex never asks you to share your account password or to set up an API key with withdrawal permissions enabled.

When you create the key on Deribit Spot for use with Mantapex, restrict its permissions to read-only access (sometimes labelled "view", "read", "query" or "info"). Mantapex only needs to fetch balances, trade history and open positions. Withdrawal, trade-execution and transfer scopes should remain disabled. If Deribit Spot offers a granular permission model, the safest combination is: enable "Read" or "View", disable "Trade" or "Spot trade", disable "Withdraw" or "Universal Transfer", and leave any margin / futures permission switched off unless you specifically want those positions visible inside your portfolio dashboard.

Some exchanges — Binance, OKX, Bybit, Bitget, KuCoin and several Asia-Pacific venues — offer an optional IP whitelist when you create the API key. Leaving the whitelist empty lets the key authenticate from any address, which is the simplest setup for use with a cloud-hosted dashboard such as Mantapex. If Deribit Spot forces you to enter at least one IP and you don't have a static address, you can usually use a placeholder value the exchange recognises (for example "0.0.0.0/0" or the wildcard option) — consult Deribit Spot's API documentation before relying on that workaround. Either way, the credentials remain in a read-only scope and cannot be used to move funds off the venue.

Credential schema sourced directly from the CCXT integration manifest used by Mantapex. Deribit Spot may rotate or extend its API in the future — if the exchange asks for a credential not listed here when you create the key, you can safely ignore it for the purpose of a read-only Mantapex import.

Offizielle Ressourcen & Community für Deribit Spot

The links below point to first-party Deribit Spot properties. We track them so you can verify announcements, support channels and operator-published policies directly at the source rather than from third-party copies. External destinations open in a new tab and are marked nofollow per our resource-link policy.