CoinOne
Connect CoinOne
Sign in to connect your exchange and track your portfolio automatically
CoinOne at a Glance
Key facts about CoinOne 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
- 0/10
- Available in
- 1 jurisdictions
- Trading incentives
- Not offered
- CCXT integration
- Supported
- coinone
Trading access & integration
CoinOne 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 CoinOne 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.
Connection metadata is read directly from Mantapex's CCXT integration manifest — credential requirements reflect what CoinOne itself exposes to read-only API consumers and may evolve as the venue updates its API.
Getting Started with CoinOne
Log In to Your Coinone Account
- Navigate to Coinone and sign in with your credentials.
Access the API Management Section
- Click on "More" in the top menu.
- From the dropdown, select "API".
- On the API page, click on "API Management".
Create a New API Key
- Click the "New API Key" button.
- Assign a recognizable name to your API key (e.g., "OctopusTracker") to identify its purpose.
Set Permissions to Read-Only
- In the permissions section, select only the necessary scopes for read-only access.
- Ensure that permissions related to actions like placing/canceling orders or withdrawals are not selected.
Generate the API Key
- Click on the "Create" or "Generate" button to create your API key.
Securely Store Your API Credentials
- After creation, your API Key and Secret Key will be displayed.
- Important: Make sure to securely save both keys, as the secret key will not be displayed again.
Account, custody & security on CoinOne
CoinOne 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 CoinOne, 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 CoinOne — operates under some form of KYC ("Know Your Customer") and AML ("Anti-Money-Laundering") obligations imposed by the jurisdiction it serves. Jurisdictional details for CoinOne 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 CoinOne 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 CoinOne 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 CoinOne's API until CoinOne itself invalidates it.
How to connect any exchange securely
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 CoinOne's exchange-specific policies — fund-segregation model, proof-of-reserves cadence, insurance coverage and incident-response history — the canonical references are CoinOne's own Help Centre and any audit reports or attestations the venue publishes directly.
API access details for CoinOne
Connecting CoinOne as a read-only portfolio source on Mantapex relies on the credentials defined by CoinOne'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 CoinOne doesn't ask for that field at all.
In short, CoinOne requires 2 credentials to authenticate API requests: API key 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 CoinOne 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 CoinOne 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 CoinOne 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 CoinOne'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. CoinOne 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.
Official resources & community for CoinOne
The links below point to first-party CoinOne 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.
Related exchanges & comparisons
Top exchanges by trust score
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.
Recent CoinOne news
Latest reporting from major crypto news outlets covering CoinOne.
- Coinpaper
Coinone Lists RLUSD, Bringing Ripple Stablecoin to South Korea
Ripple's RLUSD launched on Coinone with KRW trading in South Korea as Ripple Treasury added XRP and RLUSD support for enterprise finance.
- Coindesk
Crypto Exchange Coinone Wins South Korean Court Battle Over Doubled Bitcoin Withdrawals
Coinone won an appeal to force five of customers to return bitcoin (BTC) they managed to double withdraw from the South Korean crypto exchange over a glitch in 2018.
- The Currency Analytics
Ripple Brings RLUSD Stablecoin to South Korea's Coinone Exchange
Ripple just launched RLUSD on Coinone. The move gives South Korean traders direct access to the company's dollar-pegged stablecoin through one of the country's biggest crypto…
- CoinPedia
Ripple Lists RLUSD on South Korea's Coinone to Cap a Month of Major Expansion
Ripple just handed South Korean traders direct access to RLUSD. The stablecoin is now live on Coinone, one of South Korea's largest regulated cryptocurrency exchanges, with Korean…
- Coingape
Ripple USD (RLUSD) Enters South Korea with Coinone Listing
Ripple USD (RLUSD) stablecoin expands into South Korea's crypto market, with listing on Coinone crypto exchange on Wednesday. Traders can now access Ripple's fully-reserved,…
- Bitcoin
Ripple Expands RLUSD Access in South Korea With Coinone Listing
Ripple expands RLUSD into South Korea, opening direct KRW access on a major exchange as its stablecoin strategy continues to expand across global regulated markets and gains…
- Coinpaper
Shiba Inu Wallet Accumulates $9.45M in SHIB Through CoinOne — Identity Still Unknown
An unidentified wallet has withdrawn SHIB exclusively from CoinOne for two years, amassing $9.45M.
- Invezz
AI16Z hit with DAXA trading alert, Bithumb and Coinone issue investment warning
South Korea's cryptocurrency market is witnessing heightened scrutiny over AI16Z, a token that has recently rebranded as ElizaOS (ELIZAOS) following a contract migration.
Data Disclaimer
Exchange data is sourced from third-party providers and may not reflect real-time conditions.
Your Exchange Portfolio — Free Forever
Connect read-only API keys to see balances, orders & trade history. Mix with wallets, Polymarket & Kalshi — one portfolio for everything.
