Rate Limits
Pylontech OpenAPI applies rate limits to maintain stable and fair access for partner integrations. Quotas are defined by API category and enforced per device.
API Rate Limiting Quota Table
| API category | limit | Additional constraint |
|---|---|---|
| Site & Device | 2 requests/min | Standard pagination applies. |
| Telemetry Data | 2 requests/min | Historical data is limited to 30 days. Batch queries support up to 50 devices or sites per request. |
| Energy & Alarm | 2 requests/min | Energy statistics: Day ≤30 days; Month ≤12 months. Alarm queries are limited to 30 days. |
| Configuration | 2 requests/min | Batch updates support up to 50 devices per request. |
| Schedule | 2 requests/min | TOU schedule batch updates support up to 100 devices per request. |
| Command | 2 requests/min | Command history is limited to 30 days. Batch commands support up to 50 devices per request. |
Rate Limit Response
When the applicable limit is exceeded, OpenAPI returns HTTP 429 Too Many Requests:
json
{
"message": "Too Many Requests",
"reason": "Rate limit exceeded: 2 requests per minute per device."
}See API Responses for the HTTP response definition.