2. Rate Limiting Strategy

To maintain system stability, the FoxCloud platform enforces strict rate limiting based on two distinct dimensions: Daily Quota (total daily calls) and Frequency Limit (calls per second).

2.1 Daily Quota (Per Client ID)

The total number of API calls allowed per day is calculated based on the number of devices bound to your client_id.

Calculation Rule: Each inverter device bound to your client_id adds 1,440 calls to your daily quota pool.

Example: If your client_id has 100 inverters bound, your total daily quota is 100 * 1,440 = 144,000 calls.

Scope: This quota is shared across all APIs under the same client_id.

2.2 Frequency Limit (Per Interface)

To prevent high-frequency polling, rate limits are applied at the interface level. The limit is calculated using a composite key:
Unique User ID + Interface Identifier + Device SN (if applicable).

Note on User ID:
When using an OAuth token, the User ID is the main account ID associated with the client_id.

Frequency Tiers by Action Type:

Action Type	Frequency Limit	Calculation Key
Query / Data Fetch	1 call / second	User ID + Interface + Device SN
Insert / Update / Control	1 call / 2 seconds	User ID + Interface + Device SN

2.3 Handling Rate Limit Errors

Exceeding either the daily quota or the frequency limit will result in the following error response:

Error Code: 40404

Message: REQUEST_EXCEEDS_THE_LIMIT

Best Practice: Implement an exponential backoff retry strategy in your application when encountering a 40404 error. Note that limit calculations are based on server performance, and the Company reserves the right of final interpretation.

2.1 Daily Quota (Per Client ID)#

2.2 Frequency Limit (Per Interface)#

2.3 Handling Rate Limit Errors#

2.1 Daily Quota (Per Client ID)

2.2 Frequency Limit (Per Interface)

2.3 Handling Rate Limit Errors