Ir al contenido principal
Mantapex
BitMEX
CoinGecko·N/A rank·0 BTC vol 24h·N/A

Conectar BitMEX

Inicie sesión para conectar su exchange y rastrear su cartera automáticamente

BitMEX at a Glance

Key facts about BitMEX 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.

Puntuación de Confianza
0/10
Active markets
14 pairs
Available in
1 jurisdictions
Trading incentives
Not offered
CCXT integration
Supported
bitmex

Acceso de trading e integración

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

Compatible con CCXT Clave API requerida Secreto de API requerido Guía de configuración disponible

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

Getting Started with BitMEX

  1. Log into Bitmex: Access your Bitmex account and verify that two-factor authentication (2FA) is properly configured.
  2. Navigate to API Keys: Find the 'API Keys' section in your account settings. This is where you'll manage all your API connections.
  3. Create New API Key: Select 'Create New API Key' to begin the setup process. Your new key will serve as your bot's secure access point to Bitmex.
  4. Name Your API Key: Set a clear, descriptive name that helps identify the key's purpose:
    • Include the trading type (e.g., "Spot-Bot")
    • Add any specific strategy identifiers Good naming helps manage multiple API keys effectively.
  5. Configure API Key Permissions: Enable these essential permissions:
    • Order management
    • Position access
    • Funding information Keep permissions minimal for optimal security.
  6. Finalize API Key Setup: Complete the setup process:
    • Review all settings
    • Verify permissions
    • Complete any required 2FA steps Save your API credentials securely.

LEARN MORE

Required Credentials: Clave API Clave Secreta

Cuenta, custodia y seguridad en BitMEX

BitMEX 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. Year of incorporation is not published in our index for BitMEX, so we cannot quote an exact operational tenure here — the venue's own About page is the authoritative reference.

Almost every major centralised exchange — including BitMEX — operates under some form of KYC ("Know Your Customer") and AML ("Anti-Money-Laundering") obligations imposed by the jurisdiction it serves. Jurisdictional details for BitMEX are not surfaced in our index, so consult the exchange's own Terms of Service and Help Centre for the canonical KYC matrix. 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.

For the specific case of connecting BitMEX 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 BitMEX 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 BitMEX's API until BitMEX itself invalidates it.

Cómo conectar cualquier exchange de forma segura

Enable two-factor authentication on the exchange 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, or Google Authenticator); SMS-based 2FA is the weakest common method because of SIM-swap risk. Keep the recovery phrase or backup codes in offline cold storage rather than the same password manager you sign in with. Where the venue offers a withdrawal-address whitelist, turn it on: it shrinks the blast radius of a stolen key or hijacked session because funds can only leave to a pre-approved address after a cool-down. Pair that with anti-phishing codes, a dedicated email account, and alerts for new logins, withdrawal requests and API-key creation — most exchange-related losses originate from compromised individual accounts, not platform-wide breaches.

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

Detalles de acceso a la API de BitMEX

Connecting BitMEX as a read-only portfolio source on Mantapex relies on the credentials defined by BitMEX'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 BitMEX doesn't ask for that field at all.

Clave API
Public identifier that pairs your read-only access with your exchange account.
Secreto de API
Private signing string used to authenticate each request — never share it.
Frase de contraseña API
Additional passphrase set when the key is created (KuCoin, OKX-style models).
UID de cuenta
Numeric account identifier that some venues require alongside the API key.
ID de subcuenta
Used when the venue scopes API access to a specific sub-account.
Nombre de inicio de sesión
A separate username distinct from email, used by a small number of CCXT-supported venues.
Secreto TOTP / 2FA
Time-based one-time-password seed for endpoints that demand a fresh 2FA code.
Clave privada de la billetera
Self-custody signing key — required only by DEX / on-chain integrations.
Dirección de la billetera
On-chain address tied to the private key for DEX-style integrations.
Token bearer
OAuth-style bearer token, occasionally used in place of an HMAC API key pair.

In short, BitMEX requires 2 credentials to authenticate API requests: Clave API and Secreto de API. 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 BitMEX 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 BitMEX 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 BitMEX 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 BitMEX'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. BitMEX 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.

Recursos oficiales y comunidad de BitMEX

The links below point to first-party BitMEX 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.

Exchanges relacionados y comparativas

Peer sets sourced from CoinGecko's trust-score ranking and CCXT's exchange manifest. Inclusion here is not an endorsement — it simply means Mantapex tracks the venue with current trust / volume data.

Noticias recientes de BitMEX

Latest reporting from major crypto news outlets covering BitMEX.

Aviso sobre los Datos

Los datos del exchange provienen de proveedores externos y pueden no reflejar las condiciones en tiempo real.

Su Portafolio de Exchange — Gratis Para Siempre

Conecte claves API de solo lectura para ver saldos, órdenes e historial de operaciones. Combínelo con billeteras, Polymarket y Kalshi — un portafolio para todo.

Polymarket
Kalshi
50+ Chains
40+ Exchanges
DeFi
NFTs
16K+ Tokens
Claves de solo lectura· Encriptado· Sin acceso de trading