API credentials are important authentication information for accessing account services. Users should set necessary permissions based on their actual use and follow the principle of least privilege.

Programs used solely for data queries should not be granted trading permissions. Discontinued API credentials should be promptly closed or deleted.

Do not upload API keys to public codebases, chat tools, websites, or other unprotected environments, and do not share full API credentials with unverified third parties.

If unknown access, abnormal orders, or credential leaks are discovered, relevant API permissions should be promptly suspended and account security status checked.

Data returned by the API may be affected by market changes, network transmission, system synchronization, and service status, and there may be temporary differences from platform pages.

Submitting an order via the API does not mean the order has been completed. Developers should confirm the final result based on order status, transaction records, and account information, and set up reasonable mechanisms for duplicate request control, abnormal pause, and log recording.

Automation programs may amplify the impact of parameter errors, network anomalies, or program logic issues. Users should set order quantities, trading scope, and risk limits according to their own needs.

To maintain stable platform operation, ANMREX may impose rate limits and manage API access based on interface type, account permissions, request frequency, and system status.

API services may be adjusted, delayed, or temporarily unavailable due to system maintenance, technical upgrades, network anomalies, security management, or other reasonable reasons.

Developers should establish necessary exception handling and service recovery mechanisms and avoid circumventing platform access restrictions through repeated requests or other means.

Users can choose whether to use third-party programs or services to connect to ANMREX API.

Third-party tools may pose risks such as credential leakage, abuse of privileges, data delays, program errors, and service interruptions. ANMREX does not endorse or warrant unverified third-party tools.

Users should independently evaluate relevant services and only grant permissions necessary to complete specific functions.

Users must not use the API to conduct unauthorized access, interfere with platform operations, bypass permission restrictions, submit malicious requests, or engage in other activities that violate platform rules and applicable requirements.

If abnormal calls, security risks, or improper use are found, ANMREX may restrict, suspend, or terminate relevant API permissions based on actual circumstances.

This page is only for introducing the general service scope and usage principles of the ANMREX API, does not constitute a complete technical interface specification, and does not mean that all features mentioned in this article are fully open.

Specific API addresses, authentication methods, parameter structures, call restrictions, and available functions should be subject to the latest API technical documentation from ANMREX and the actual display in the account dashboard.

API services cannot completely avoid delays, interruptions, data discrepancies, or other technical risks. Users should properly manage API credentials, access permissions, and program running status.

If you have questions about the ANMREX API, please email support@anmrex.com.

Please specify the relevant features, the time of the issue, and any necessary error information in your email. Do not send full API keys, account passwords, or verification codes.