Customers use their own exchange accounts to create API connections and retain control over their funds and accounts. OQIRON only uses the trading permissions necessary to run strategies and does not require access to withdrawal permissions.
The core of the personal exchange API mode is that “funds remain in the customer’s exchange, and trades are executed by the system within the authorized scope.” Customers continue to view their funds and accounts through their own exchanges, while granting OQIRON the limited permissions required to read account status and execute strategy trades.
In individual API mode, the trading principal remains in the customer’s own exchange account.
Customers do not need to transfer their principal to the platform; their balances, open positions, and trading history remain on their own exchanges. The platform executes strategies via a restricted connection without altering the accounts where the funds are held.
The connection does not require withdrawal permissions, and customers should not grant this permission to anyone.
Withdrawal permission does not block API binding or robot Start, and OQIRON never uses a customer trading API to withdraw.
Customers retain control over exchange logins, API revocation, and fund management.
Customers retain control over exchange logins, fund allocation, and API revocation. This control also means that customers are responsible for maintaining account security and must avoid making arbitrary changes to an open position while the bot is running.
Keeping funds in the client’s exchange is only the first consideration. Clients also need to understand what permissions the API requires, what to check before launching the system, how to handle connection failures, and how to safely close existing positions after the service is stopped.
Customers do not need to transfer their trading capital to the platform account; they can still view their balances, positions, and funds through their own exchanges.
Activating this mode does not require transferring your principal to the platform. Your balance, open positions, and trading history remain in your own exchange account; therefore, you are responsible for understanding the security, service stability, and usage rules of your chosen exchange.
The API is used to retrieve account status and execute strategy trades; it does not require withdrawal permissions. The system should not begin operation if permissions are set incorrectly.
API permissions should only include the capabilities required for reading and trading; withdrawals should not be enabled. The system will verify the API key, permissions, account mode, and necessary connection conditions; if permissions are incorrect or the system cannot read the live account status, automated trading will not begin immediately.
Customers can view connections, revoke API access, or adjust funding arrangements on the exchange; the system operates within valid authorizations and risk limits.
Customers retain the right to log in to exchanges, manage funds, and revoke API access at any time. Revoking, deleting, or modifying an API will cause the system to lose its ability to read or execute data; the customer dashboard should clearly display a connection error rather than continuing to show the system as operational.
The Individual API Mode requires a valid trial or subscription, and service fees are calculated based on eligible, settled positive net returns in accordance with account activation rules.
Individual Mode requires a valid trial or subscription. Subscription fees cover the use of the system’s services and do not constitute trading capital; profit service fees are calculated solely on eligible net profits that have been settled, in accordance with the rules in effect in the customer’s account at the time.
Use API credentials dedicated to OQIRON. Never send login passwords, email verification codes, or complete keys through support, chat apps, or screenshots.
Withdrawal permission does not block API binding or robot Start, and OQIRON never uses a customer trading API to withdraw.
Permission labels vary by exchange. After binding, the system still verifies account identity, read access, trading permissions, and position mode.
After the connection is saved, the system will verify the exchange, account identity, position mode, data retrieval capabilities, and trading permissions in the background. Successful saving of the information only indicates that the configuration is complete; it does not mean the bot has been authorized to run.
Customers can log in to the exchange to view their balances, positions, and orders, and can also revoke API access or adjust their funds. At the same time, customers must ensure the security of their exchange login credentials and avoid arbitrarily changing position modes, permissions, or specific system positions while the bot is running.
If a customer manually closes a position, modifies a stop-loss order, or cancels a system order on an exchange, the affected position may transfer to the customer’s control. The system will stop adding to or modifying positions with an unclear status until ownership and status have been verified.
Free trials are issued by customer service based on current eligibility; paid subscriptions take effect after purchase by the customer. Both are limited to individual API mode service eligibility; the API, funds, risk assessment, and account status are still subject to separate review.
Once the license expires, the system immediately blocks the addition of new risk, but you cannot simply shut down the process and leave open positions. Existing pending orders, open positions, protection orders, executed trades, and final reconciliation must undergo a controlled exit; only after this process is complete can the bot be fully stopped.
Complete email verification
Customers must first complete email registration and account security setup to establish a unique customer identity. Registration itself does not automatically connect to an exchange or initiate trading.
Try it or purchase a subscription
Customers should contact customer service to request a trial or purchase a currently valid subscription. Service eligibility is only one of the requirements for activation and does not replace API, funding, and risk checks.
Create and Verify API
Use API credentials dedicated to OQIRON. Never send login passwords, email verification codes, or complete keys through support, chat apps, or screenshots.
Complete Risk Preference and Verification
Execution is permitted only after selecting a risk preference and passing the funding, account, and security checks. During execution, the API and account status are continuously monitored, and new risk exposure is limited in the event of anomalies.
No, the trading principal remains in the client’s own exchange.
Withdrawal permissions should not be granted.
If the system is unable to read or execute a command, it will display an error and restrict operation; the customer will need to recheck the connection.
Yes, customers always retain control of their exchange accounts.
OQIRON
