1.1. This API Policy (hereinafter the “API Policy”) adopted by the company Nice Reply, s.r.o., having its registered seat at Staré Grunty 3546/7A, 841 04 Bratislava - mestská časť Karlova Ves, Slovak Republic, ID No. 46 682 007, registered in the Business Register of the City Court Bratislava III, Section Sro, Insert No. 81612/B (hereinafter the “Nice Reply”) provides guidelines and rules for the usage of the Nice Reply´s application programming interfaces (hereinafter the “API”).
1.2. The API represents all and any application programming interfaces made available by the Nice Reply including any related features, tools, documentation, codes, updates and materials in any form whether tangible or intangible (hereinafter the “Documentation”).
1.3. By accessing or using the API you agree and accept this API Policy that forms the agreement between you and the Nice Reply. Access and use of the API and associated API Documentation shall be safe and secure and shall always comply with this API Policy, Terms of Service, Privacy Policy and any applicable terms and guidelines published or provided by the Nice Reply or with the applicable law.
1.4. Terms capitalized herein and not otherwise defined shall have the meaning as set forth in the Nice Reply´s Terms of Service.
1.5. The purpose of this API Policy is to
- ensure the security, efficiency and safe operation of the API used for providing Services and
- protect the user's data.
1.6. This API Policy applies to the Clients and their developers and also to third parties upon the prior approval of the Clients and their developers as specified in point 1.6 (hereinafter the “Users”).
2.1. The Clients acknowledge that in order to access and use the API they need to have
- a registered Account and
- an API-key generated upon request by the Nice Reply after logging into the Account.
The Client also acknowledges that he may grant the access to API to third parties and their developers through the Account.
2.2. The requests for the API-key shall be sent to the Nice Reply solely in the HTTP otherwise they will be ignored.
2.3. The Clients undertake to keep the API-key and other related information confidential and secure and shall not share it with any third parties (exempt as specified in point 2.1).
2.4. The use of the API-keys may be reviewed periodically by the Nice Reply and any misuse may result in termination of the Client's access to API.
3.1. The requests to the API are not currently subject to rate limiting. Notwithstanding the stated herein, the Nice Reply reserves the right to limit such requests if it detects an unusual high-volume of requests.
4.1. By accessing or using the API, the Users undertake to comply with applicable data processing obligations mentioned in this API Policy and in the Documentation, as well as with all applicable data privacy regulations. Information about processing of personal data by Nice Reply can be found on the following website https://www.nicereply.com/privacy-statement-for-customers.
5.1. The Users acknowledge that the Nice Reply owns and holds a title to all and any API including Documentation and to all related proprietary and intellectual property rights and the Users shall not interfere with any of such rights.
5.2. Subject to this API Policy, the Nice Reply grants to the Users a non-exclusive, royalty-fee, non-transferable, non-sublicensable, revocable and limited (in terms of time and subject matter) license to use the API solely for the interaction or integration with the Nice Reply´s Application solely in order to use the Nice Reply´s Services according to the Contract and under the terms specified in this API Policy and associated Documentation (hereinafter the “License”).
5.3. License is limited by the duration of the Contract between Nice Reply and the Client and cannot be assigned, sublicensed, transferred, lent, rented, shared to any other third party without the prior written consent of the Nice Reply. License shall not be used in any way other than as specified in this API Policy and associated Documentation.
6.1. The API has only a single current version. The API is not being versioned.
7.1. Non-breaking changes, such as the addition of
- the new response fields or
- the endpoints, will be implemented without any prior notice to the Users.
Any changes to endpoints marked as Beta or Development are considered to be non-breaking.
7.2. For breaking changes such as (i) the different behavior, (ii) the endpoint removal, or (iii) the response field removal, the Nice Reply strives to provide a notice period of:
7.2.1. 30 (thirty) days for the non-critical endpoints and changes, and
7.2.1. 60 (sixty) days for the critical endpoints and changes,
(hereinafter the “Depreciation notice”).
7.3. The Depreciation notice period (as specified in point 7.2 above) will be counted from the day of the Depreciation notice.
For example, if the Nice Reply announced the changes on March 14th, the earliest depreciation date would be April 13th (allowing a full 30 days for the non-critical endpoints) and May 13th (allowing a full 60 days for the critical endpoints).
7.4. Changelog: https://cdn.nicereply.com/s/api/latest/change-log/.
8.1. The Depreciation notice period does not guarantee an immediate breaking change. Once the depreciation date has passed, the feature may be removed at any time, including immediately or several months later.
9.1. The Nice Reply may not send additional notifications when the depreciation date arrives, nor will we send the notifications specifically for the implementation of the breaking change itself. The Depreciation notice will serve as the initial notification. However, the Nice Reply will document all relevant information in the changelog.
10.1. The Users must refer to the official Documentation for the accurate usage instructions and the endpoint details and to stay informed about upcoming depreciations and any changes or updates related to the API.
10.2. The Nice Reply´s official Documentation also includes all depreciation information, together with the dates and details.
10.3. The Users acknowledge that Documentation is subject to the changes and updates and they covenant to check for any latest versions.
11.1. The Users shall report any API-related issues or outages to the Nice Reply immediately after their occurrence.
11.2. The Users acknowledge that the API is provided “as is” and the Nice Reply gives no warranty and representation whether express or implied, statutory or otherwise, including the warranty of merchantability, fitness for a particular purpose, availability at any time or non-existence of any defects or defaults, viruses or harmful features.
11.3. The Nice Reply is liable for damage caused to the Users due to access and usage of the API only if it was caused intentionally or by gross negligence excluding (to the maximum permitted by law)
- loss of profit, revenue or income,
- special, indirect or consequential loss or damage.
The aggregate liability of the Nice Reply under this API Policy and related Documentation shall not exceed the total limit as specified in Clause 12.6 of the Terms of Service of the Nice Reply.
12.1. The Users shall comply with all terms and conditions in this API Policy.
12.2. The Users acknowledge that use and access to the API is expressly conditioned on the User´s compliance with this API Policy and other Documentation provided by the Nice Reply or with the applicable law.
12.3. The Users undertake
- not to use the API for any illegal activities
- to access API only in accordance with the implementation instructions and requirement and to the extent specified in the relevant Documentation.
12.4. The Users also undertake not to:
12.4.1 access and use the API for any illegal or fraudulent activities or manners that may cause damage, breaks, degrades or are considered to be harassing, obscene, defamatory, threatening or unlawful;
12.4.2 use the API to introduce viruses, defects, malwares or other malicious elements that may breach or compromise the security of the Nice Reply´s Services or otherwise pose a security vulnerability;
12.4.3 exceed the reasonable volume of the API requests;
12.4.4 access and use the API to compete with the Services or replicate them;
12.4.5 use the License in any way not in compliance with the API Policy;
12.4.6 infringe or attempt to infringe or destroy any proprietary or intellectual property rights of the Nice Reply;
12.4.7 use, copy, lease, sell, transfer, assign, sublicense, disassemble, decompile, transmit, reverse engineer, modify, alter or otherwise use the API exempt as permitted in the API Policy.
12.5. Non-compliance or any attempted violation of this API Policy, Terms of Service and the Documentation, instructions or the applicable law may result in the API key revocation and in potential legal actions. The Nice Reply reserves the right, at its sole discretion, to assess such violations. This also applies to the situation when the Users provide the Nice Reply with untrue, incomplete, inaccurate and misleading information.
12.6. The Users acknowledge that the Nice Reply may monitor the use of the API in order to ensure the security and compliance with this API Policy.
12.6. The Users´ access and use of the API is restricted as it is set forth in this API Policy and relevant Documentation or may be restricted and limited at the sole discretion of the Nice Reply. The Users shall not attempt to exceed such restrictions while using the API.
13.1. The Nice Reply reserves the right to update, change or modify this API Policy and associated resources and the Documentation at any time as needed even without the advance notice.
13.2. The Nice Reply may notify of any API Policy updates or changes to the registered Users through appropriate channels.
13.3. The Nice Reply will not be liable for any modifications and changes and their adverse effect on the operation and functioning of the Application and the Services.
13.4. The access and use of the API may be terminated at any time through the Account.
14.1. The Nice Reply will use all reasonable efforts to provide support to any API-related issues and inquiries to the registered Users. For any API-related issues and inquiries and questions please contact: contact@nicereply.com. Feedback and suggestions: Product Roadmap.
15.1. As part of the Nice Reply´s ongoing efforts to improve its services, the Nice Reply would like to inform you that we are currently in a transition phase between the APIs. The Nice Reply is working towards depreciating the current API and introducing a new version to enhance functionality and provide a better experience for Users.
15.2. During this transition, the Nice Reply understands the importance of maintaining continuity and minimizing disruptions for our Clients. Therefore, the Nice Reply will make every effort to support the current API for a minimum of 3 (three) months from the date of this notice. This will allow you some time to plan and prepare for the migration to the new API.
15.3. The Nice Reply encourages you to review the Documentation and guidelines for the new API as they become available. The Nice Reply´s team will provide regular updates and resources to assist you in the transition process.
15.4. Please note, that while the Nice Reply aims to support the current API for at least 3 (three) months, there may be instances where certain features or endpoints will be depreciated or removed sooner. The Nice Reply will provide clear communication regarding any changes or depreciations to ensure a smooth transition.
15.5. The Nice Reply appreciates your understanding and patience during this transition period. Our goal is to deliver a more robust and efficient API that meets your evolving needs. If you have any questions or require further assistance, please do not hesitate to contact our support team.
Thank you for your continued support.
