APIs Clause Samples
The APIs clause defines the terms under which application programming interfaces (APIs) are provided, accessed, and used between parties. It typically outlines the permitted uses of the APIs, any restrictions on reverse engineering or modification, and requirements for maintaining security and confidentiality. For example, it may specify that the API can only be used to integrate with certain software or that usage data must not be shared with third parties. This clause ensures that both parties understand their rights and obligations regarding API access, helping to protect proprietary technology and prevent misuse or unauthorized disclosure.
POPULAR SAMPLE Copied 31 times
APIs. The parties acknowledge and agree that the purpose of this Section 7.3 is to promote and encourage standardized APIs for the PS Licensed Products in order to (i) assist the developer community by reducing the time, effort and cost involved in developing applications compatible with products incorporating the PS Licensed Products, (ii) provide a rich suite of interoperable applications to the end user community, and (iii) provide data compatibility between products incorporating the PS Licensed Products.
APIs. Licensee must keep Licensee’s Software that is accessing a ▇▇▇▇▇▇ ▇▇▇ API current with, at a minimum, the previous version of the API. ▇▇▇▇▇▇ Mae is under no obligation to make data or services available via an API.
APIs. APIs" means the software application interfaces and workflow methods made generally available by Licensor in certain Products to enable integration, implementation, and interoperability with third party hardware and software. If Licensor makes APIs for a given Product generally available, then the following terms will apply. You may use the API, together with applicable documentation, any sample code, and any sample applications provided with the API and that may be included as part of a Software Development Kit (“SDK”) to design, develop, and test software programs. You may (i) make a single copy of the SDK for back-up purposes only (ii) copy the runtime components of the SDK ("Runtime Component") into software code created through your use of the SDK, and (iii) reproduce and distribute such Runtime Component solely as a component of your software code. You may not use the SDK to develop, or incorporate the Runtime Component in, a product or service that competes with Products or Services. Licensor's ownership rights in Section 2 apply to any output such as the Runtime Component. The inclusion of the Runtime Components in your original code created through your use of the SDK in no way alters Licensor's ownership rights in the Runtime Component. Licensor may develop software programs substantially similar or identical to those developed by you through your use of the SDK and reserves the right to sell and distribute those software programs.
APIs. Use of the Services includes use of StarTex’s application program interface (API). Use of the API requires Customer’s compliance with the terms of this Agreement with respect to the Services. If Customer abuses, excessively uses the API, or otherwise violates any Restriction Violation, StarTex reserves the right to deny Customer access and use of the API. The Documentation may include additional restrictions on or limitations to the use of the Services, including, without limitation, limitations on API access of the Services, and Customer agrees to comply with any such restrictions or limitations.
APIs. In the event that BlueCat makes available any APIs to Customer as part of the DNS Flex Services or Cloud Services, then Customer may access such APIs on a non-exclusive, non-transferable, non- assignable basis for the applicable Subscription Period identified on a Purchase Order, subject at all times to the terms and conditions of this Agreement. Customer is responsible for making and maintaining all necessary arrangements to access, use and interface with such APIs in accordance with such specifications, restrictions and guidances as BlueCat may stipulate from time to time. In addition, APIs regarding BlueCat Gateway are subject to the requirements detailed at the following address: ▇▇▇▇▇://▇▇▇▇.▇▇/repository/bluecat/gateway and Customer agrees to comply with such requirements. BlueCat may from time to time on reasonable notice require Customer at Customer’s own cost to take such steps as are required to integrate any modifications or updates BlueCat makes to APIs. BlueCat reserves the right to restrict Customer access the APIs if BlueCat reasonably determine, in BlueCat sole discretion, that the volume of queries originating from Customer use of the APIs is unduly burdening any API.
APIs. PayPal shall make available to you its API integration and user guides and SDKs (collectively “PayPal Documentation”). You shall comply with the PayPal Documentation in connection with the integration and use of APIs. You shall keep all user ID, passwords and other access codes pertaining to the Services and API Licence confidential and secure from all unauthorised persons. You will immediately terminate the access rights of any user who ceases to act in an authorised capacity on your behalf for any reason, including because of a change in employment status or in the event of theft, loss, or authorided disclosure or misuse of that user ID. You agree to notify PayPal immediately upon learning of any unauthorised use of your user ID or password. You shall be solely responsible for (i) updating your passwords for access to the Services periodically, and (ii) creating passwords that are reasonably “strong” under the circumstances. The user ID is the property of PayPal and may be immediately revoked or terminated by PayPal if you share the same with any third party, or otherwise breach this API Licence. In connection with your use of the APIs, you are prohibited from doing any of the following: (i) selling, transferring, sublicensing, or disclosing your user ID to any third party (other than third party service providers); (ii) selling, transferring, sublicensing, and/or assigning any interest in PayPal’s confidential information accessed by the APIs; (iii) collecting any customer’s personally identifiable information that is accessed through the APIs without that customer’s express permission; (iv) providing timeshare, service bureau, application service provider, or similar services to any other third party; and (v) interfacing or connecting the Services, or the API Licence with any other computer software or system without the prior written approval of PayPal. PayPal shall have no responsibility or liability for the performance of the Services, in the event that the Services are not used in accordance with this Agreement or any instructions for use provided by PayPal.
APIs. Any user of any third party application that calls any Licensed Software application programming interfaces (“Product APIs”) must have a valid license to connect to the Licensed Software. Licensee shall not, and shall not allow others, to reverse engineer, decompile, or disassemble the Product APIs. Commercial distribution of any products that include Product APIs requires a separate distribution license and such license is not granted by this License Agreement.
APIs. We may change, discontinue or deprecate any APIs utilized for the Service from time to time but will use commercially reasonable efforts to continue supporting the previous version of any API changed, discontinued, or deprecated for 12 months after the change, discontinuation, or deprecation (except if supporting the previous version (a) would pose a security or intellectual property issue, (b) is economically or technically burdensome, or (c) is rendered impossible or impractical as a result of a requirement of the law or requests of governmental entities).
APIs. We may modify or discontinue any APIs to the Cloud Services from time to time.
APIs. GE may change, discontinue, or deprecate any application program interface utilized for the Predix platform (“API”) from time to time but shall use commercially reasonable efforts to continue supporting the previous version of any API changed, discontinued, or deprecated for 12 months after the change, discontinuation, or deprecation (except if supporting the previous version would pose a security issue or is rendered impossible or impractical as a result of a legal or technological requirement).