What Is an Api License Agreement

E. Termination Termination. Upon termination of this Agreement, your licenses for the Marketo APIs and API Specifications under Sections 2.A (Marketo API License) and 2.B (Marketo API Specification License) will terminate immediately. Notwithstanding the foregoing, Sections 2.C (Marketo Feedback License), 3 (Warranty, Disclaimer, Indemnification and Limitation of Liability), 4 (Confidentiality) and 6 (Miscellaneous) shall survive termination of this Agreement. 2.2 Subject to this Agreement, including the limitations set forth in Section 3, Zendesk grants Licensee a non-exclusive, non-transferable, non-sublicensable, worldwide, and revocable right and license during the Term (as defined in Section 13) to: (a) use and access the API to develop Applications solely for use by Subscribers in connection with the Services; implement and distribute; (b) use and display the Marks only to determine that the Service Data originates from the Services; and (c) market and sell Applications through the Marketplace in accordance with this Agreement. 2.2. No sublicense. All license rights granted herein are granted exclusively to you and may not be sublicensed, transferred or assigned, except as otherwise provided herein. 1.1. API License. Subject to the terms of this Agreement, Rebilly grants you a non-exclusive, non-transferable, non-sublicensable, limited license to use the Application Programming Interface (“API License”) only in accordance with the terms of this Agreement.

The API license only allows you to: Some companies may open their API to third-party developers without an API license agreement (“go naked”), but this can cause problems and cause companies to later create a license and restrict what developers do. This article uses Twitter as an example. Twitter had previously given developers very liberal access to their API, but developers used their API to duplicate their interface and compete with them, so Twitter made changes to its API agreement. D. Marketo API License Restrictions. Marketo reserves the right to use the Marketo APIs under this Agreement, and you agree not to remove or modify any copyright (by .B. “© Marketo, Inc.”) or any other proprietary notice identifying Marketo`s ownership of such title. In addition, you accept and agree to the following license restrictions: (i) no rights under this Agreement are granted to market, distribute or use the Marketo APIs (or to sublicense any of the foregoing rights); (ii) under no circumstances will you make the Marketo APIs available as source code to an end user or any other third party; (iii) none of the following rights are granted in connection with the Marketo APIs: the right to distribute, publicly display, or create derivative works (e.B. a superset or subset of the Marketo APIs); and (iv) the Marketo APIs may not be used to access any service other than the Marketo Solution. Marketo may limit the number and/or frequency of API requests to the Marketo Solution or any use of the APIs that could damage, disable, overburden, alter or otherwise alter the Marketo Solution. If you would like to obtain a commercial license of Marketo APIs to sublicense Marketo APIs in combination with your products (including your software application), please see launchpoint.marketo.com/ to learn more about Marketo LaunchPoint membership. 5.

Proprietary Rights. Between the parties, the Company owns all right, title and interest in and to all editions and executables of the APIs, and subject to the foregoing, Licensee owns all right, title and interest in and to the Application. Except to the limited extent expressly provided in this Agreement, neither party grants any right, title or interest (including, but not limited to, implied licenses) in or to any property of the first party and the other party may not acquire them. All rights not expressly granted herein shall be deemed to have been denied. When selling an API, the incentives between the company providing the API and the companies that use it may not be perfectly aligned. For this reason, it is important to have a license agreement that (i) describes the expectations of external developers to use the API, (ii) communicates what developers are allowed to do with the API, and (iii) assigns the risk of loss in the event of problems using the API. It is necessary to resolve these issues in the license agreement to reduce potential liability and prevent unintended outcomes. Some of the ways to achieve this include communication in the license agreement: the article points out that API licensing agreements are important because circumstances can change, and the contract can protect the API owner if changes need to be made to the way developers access the API or the API itself. It can also allow the owner to set the expectations and standards they have for third-party developed applications. The agreement usually includes terms that allow the company to unilaterally modify the agreement at any time, as well as limitations of liability. 3.1 Licensee shall comply with all restrictions set forth in this Agreement, the Privacy Policy and the General API Guidelines for all uses of the API and Service Data and the publication of the Applications.

Licensee shall also comply with all restrictions set forth in this Agreement and the Trademark Use Guidelines. If Zendesk believes, in its sole discretion, that Licensee has violated or is attempting to violate any provision, condition, or spirit of this Agreement, Licensee may be terminated temporarily or permanently under this Agreement with or without notice to Licensee. (ii) Unless otherwise limited by the Application Terms of Use imposed or required by Licensee, Licensee grants Subscriber a perpetual, worldwide, non-exclusive, non-transferable, non-sublicensable license to access, provide, use and integrate the Application in connection with Subscriber`s active account for a Service. 14. Termination. This Agreement shall survive until terminated as set forth in this Section or for the duration set forth in the applicable Services or the Purchase Order entered into by the Parties. Either party may terminate this Agreement at any time. Any termination of this Agreement will also terminate the licenses granted hereunder. Upon termination of this Agreement for any reason, Licensee shall destroy and delete all copies of the Company`s Confidential Information from all computers, hard drives, networks and other storage media and confirm to the Company that such actions have taken place. Sections 4, 5 and 10 to 17 (and all accrued payment entitlements) shall survive termination of this Agreement.

7.2. No advice or information, oral or written, received by you from HitBTC or through or the API creates any warranty not expressly set forth in this Agreement. HitBTC does not warrant that the API and Documentation are suitable for Use by Licensee, that the API or Documentation is free of errors or errors, that operation will be uninterrupted or that defects will be corrected. In addition, HitBTC does not guarantee the results of using the API and documentation. 10. Confidentiality. The API (including, but not limited to, all enhancements, derivatives, modifications and the like) constitutes Company Confidential Information (“Confidential Information”). Licensee hereby agrees to (i) keep Confidential Information confidential and take reasonable precautions to protect such Confidential Information (including, but not limited to, the precautions Licensee takes with respect to its own Confidential Materials), (ii) not to disclose Confidential Information to third parties (other than consultants, subject to the terms and conditions set forth below), (iii) not to use Confidential Information except for the purposes set forth for that purpose.

Agreement and (iv) not to copy or reverse engineer any Confidential Information. . . .