OQIRON
Grant only the necessary permissions
Personal account mode requires read and trading permissions. Permission names vary by exchange, so use Oqiron's permission check after linking as the authority. Withdrawal permission does not block API linking or bot startup, and OQIRON does not use a customer's trading API to make withdrawals.
Protect API credentials
Neither the Oqiron client interface nor the admin interface should display full private keys. Switching APIs should not delete existing historical orders or profit records.
- Do not send your API Secret or Passphrase via chat apps, email, or screenshots.
- Do not store full credentials in public documents, cloud-based note-taking apps, or code repositories.
- If you detect a security breach, unusual logins, or unknown transactions, immediately revoke your old API key on the exchange, then contact platform support.
Linking does not mean activation
After the API is successfully created, the system will also verify identity, read permissions, trading permissions, position mode, and other activation conditions. If any key details cannot be verified, the bot will remain inactive.
Support Scope and API Replacement
The customer dashboard currently provides integration options for OKX, Binance, Bybit, Gate, and Bitget; however, whether each exchange can be used for live trading must be determined based on the actual verification results for that account. Before replacing or deleting an API, you must first safely stop the relevant bots; once a new API passes verification, historical order and profit records should remain intact.
An API is like a specialized key—the fewer permissions it has, the more secure it is.
The API allows the system to read account information and execute trades without requiring customers to provide their exchange passwords. When creating an API, use one dedicated exclusively to Oqiron—do not share it with other bots—and set IP restrictions according to the exchange’s policies. Permissions beyond reading and trading should not be granted in advance simply because they “might be needed later.”
After a private key is compromised, simply removing the binding from the OQIRON page will not invalidate the old private key; you must return to the exchange to revoke it. After recreating the account, the system will need to re-verify read permissions, contract permissions, account mode, and position mode; do not assume that “Saved Successfully” means “Verification Passed.”
After reading this, what should customers be able to do?
Truly understanding a knowledge article isn’t about memorizing a few terms, but about being able to make the right decisions based on actual page content and account status. Use the checklist below to verify whether you’ve grasped the key points.
- Use a dedicated API that is not shared with other services
- Grant only read and necessary trading permissions
- Always keep withdrawal and fund transfer permissions disabled.
- Safely stop the robot before replacement; if credentials leak, revoke the API at the exchange first.
Frequently Asked Questions
These questions are directly related to the content of this article. Answers are based on current platform rules and actual operational standards; however, when it comes to packages, percentages, the scope of available features, or account status, the information displayed on the customer dashboard and official statements shall prevail.
- What permissions does the exchange API require? | Personal accounts require read and trading permissions; use Oqiron's permission check after linking for the exact names. Withdrawal permission does not block API linking or bot startup, and OQIRON does not use a customer's trading API to make withdrawals.
- Will customer service ask me for my API Secret or mnemonic phrase? | No. Do not send your API Secret, passphrase, private key, mnemonic phrase, or password via online customer service, Telegram, WhatsApp, or any other chat platform.
- Will switching APIs result in the loss of historical data? | It should not. Please safely stop the relevant bots before switching; the new API will need to be re-verified. Existing orders, positions, and profit history should be retained by client and bot, and will continue to exist without relying on the old API key.