Terms of Use
These Terms of Use govern access to and use of Pylontech OpenAPI by an approved partner, developer, or application operator ("API User"). By using the API, the API User agrees to these terms and any applicable partner or service agreement with Pylon Technologies Co., Ltd.
1. Access to the API
API access is available only to approved API Users. Pylontech may determine operations and usage limits available to each client application.
Credentials and access tokens are issued for the API User's authorized application and may not be transferred, shared, sublicensed, or used by an unapproved third party.
2. Authorized Use
The API User may use OpenAPI only for the integration purpose approved by Pylontech and only for sites and devices for which the API User has valid authorization.
The API User must not:
- access or attempt to access a site, device, account, or data outside its authorization scope;
- bypass authentication, authorization, rate limits, or other technical restrictions;
- interfere with the availability, security, or operation of Pylontech services;
- use the API to introduce malicious code;
- use data in any manner that violates applicable law or the rights of a site owner.
3. Site Owner Authorization
Where access depends on a site owner's authorization, the API User is responsible for obtaining and maintaining that authorization. The API User must stop accessing the affected resources when authorization is revoked, expires, or is otherwise no longer valid.
4. Credentials
The API User is responsible for all activity performed with its credentials and tokens. It must prevent unauthorized disclosure and notify Pylontech promptly if credentials or tokens are lost, exposed, or suspected to have been compromised.
Pylontech may revoke credentials when required for security.
5. Data
The API User may collect, process, retain, and disclose API data only to the extent necessary for the authorized integration and in accordance with applicable privacy, data-protection, and confidentiality obligations.
When authorization ends, the API User must cease new collection and handle previously collected data as required by applicable law and its agreement with the site owner.
6. Device Control
The API User is responsible for commands, schedules, and configuration changes submitted through its client application.
Before enabling device-control functionality, the API User must ensure that it has the authority to control the target device and that the requested action is appropriate for the applicable site, device capability, grid requirements, and operating conditions.
Pylontech may reject, cancel, or limit a control operation where the requested operation is unsupported, conflicts with device or platform constraints, or could affect safe and reliable operation.
7. Availability and Changes
Pylontech may deprecate an API, data schema, or environment. Where reasonably practicable, material changes will be communicated through applicable partner channel.
OpenAPI may be unavailable during maintenance or because of network, cloud, device, or third-party conditions. Unless otherwise agreed in writing, no specific service level is created by these terms.
8. Intellectual Property
Pylontech and its licensors retain all rights in OpenAPI, its documentation, Pylontech services, trademarks, and related technology. These terms grant only the limited right to use OpenAPI for the approved integration.
9. Suspension and Termination
Pylontech may suspend or terminate API access when the API User violates these terms, exceeds the approved scope, creates a security or operational risk, or when suspension is required by law or an applicable agreement.
When access ends, the API User must stop using the credentials, tokens, and API endpoints provided by Pylontech.
10. Responsibility and Liability
The API User is responsible for its application, its use of API responses, and the effects of control requests it submits. Limitations of liability, warranties, indemnities, and governing law are determined by the applicable written agreement between Pylontech and the API User and by applicable law.