1. API Authorization and Permission Allocation
AOZX provides REST API and WebSocket interface services to quantitative investors and institutional clients. Users must follow the following security rules when using API functions:
Principle of least privilege: When creating an API Key, users should accurately select permissions according to business needs, such as enabling only "read" or "trade" permission. Enabling "withdrawal" permission for non-custodial interfaces is strictly prohibited.
Security hardening: API keys must be bound to fixed IP allowlists. The Platform assumes no liability for asset security incidents caused by a user's failure to bind an IP allowlist or by key leakage.
2. Rate Limits
To ensure the stability and fairness of the Platform matching engine, AOZX imposes strict frequency limits on API requests:
Rate-limit standards: The system allocates specific per-second or per-minute request limits (Weight/Count) according to the user's VIP level and interface type, such as order placement, order cancellation, or market-data queries.
Violation handling: If a user exceeds the frequency limit by malicious high-frequency requests, distributed scripts, or crawler programs, the system will automatically trigger protective mechanisms and may take punitive measures including temporary suspension of API permissions, IP blocking, and even suspension of account trading.
3. Disclaimer and Service Changes
API services are provided on an "As-Is" and "As-Available" basis. AOZX does not guarantee that API interfaces will be free from interruption, delay, or errors. The Platform assumes no compensation liability for API trading failures or liquidation losses caused by system upgrades, network failures, or matching delays.