Announcement on HashKey Exchange's management rules of sub-accounts and API Keys – HashKey Exchange

Overview

These rules apply to all users who use API or sub-accounts to query data and place orders at HashKey Exchange (hereinafter referred to as the Exchange), including Retail and PI clients, market makers and Omnibus users.

The “API” in these rules refers to the Application Programming Interface (API) provided by the Exchange. By programming, users can get the public market data (Public Market Data) and private data (Private Data) provided by the Exchange through the application programming interface, and perform Order Management, such as placing and canceling orders.

The "sub-account" in these rules refers to the trading sub-account opened by the user under its main account. In the sub-account, users can perform asset transfers and transactions at HashKey Exchange.

Effective date

The effective date of this rule is 2024/2/1 00:00:00 (UTC+8).

Creation and management of sub-accounts and API Keys
- The number of sub-accounts and API Keys that users can create at the Exchange is limited by their user type and level. The default maximum number and level for users are shown in columns (A) and (C) in Table 1 respectively.
  
  Table 1 Number limits of Sub-account & API Key and API rate limit for different user type and level

Before applying for an API key, user needs to be familiar with the principles of the API, understand the risks of the API, and fill in the corresponding questionnaire and usage statement.
If the number of sub-accounts, the number of API keys and the API rate limit for a user doesn't meet the requirements, the user can submit a request or send an email to customer service or sales team with a reasonable explanation to apply for the promotion on the number or the level. The maximum limits that can be applied for promotion are shown in B, D and F of Table 1 respectively.
The Exchange reserves the right to reject the application for promotion due to unreasonable reasons or system security considerations.
For users who successfully get promoted on the number or level, the Exchange will regularly evaluate their sub-accounts and API usage. For sub-accounts or API Keys that have been inactive for a long time or are rarely used, the Exchange reserves the right to withdraw the promotion or lower the rate limit.
For sub-accounts or API users that have abnormal operations (such as conducting Contra Trade, Wash Trade, frequently sending invalid requests through API, etc.) and do not comply with usage specifications, the Exchange reserves the right to freeze all existing sub-accounts or APIs. or some functions, and prohibit the opening of new sub-accounts or API operations.
Users can apply to freeze some or all permissions of existing sub-accounts or APIs after submitting corresponding materials (such as account theft, password leakage, etc.).
The Exchange reserves the right to adjust the numbers in Table 1. Please pay attention to the latest relevant announcements for the latest rules.

4. API rate limit rules
- The user's API rate limit level is divided into two categories: public interfaces which are subject to rate limit restrictions on the IP level and private interfaces which are subject to rate limit on API Key and main account level respectively.
- The Exchange set rate limits for query and order respectively on the API key level and on the main account level. Please contact your account manager for details.
- The Exchange reserves the right to adjust the above API rate limit levels and the corresponding number based on actual usage. For the latest API rate limit rules, please stay tuned for the latest relevant announcements.

Related articles