We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

API Licence Sample Clauses

API Licence. In consideration of the User becoming bound by and continuing to comply with the API User Agreement, Nord Pool grants to the User a non-exclusive, non-transferable, non-sub-licensable, world- wide, revocable right and license to use such API(s) as it requires to send and transmit data to the extent necessary to interface with one or more of Nord Pool’s systems and/or markets.
API Licence. (a) Once the Customer has created an account on ProcurePro, in consideration of the Customer’s payment of the Fees, the Supplier will supply the Customer with the API in accordance with clause 3.1. (b) The Supplier may provide the Customer with specifications that give the Customer guidance to establish the required interfaces between the Customer’s systems and the API (Documentation). (c) The Customer is responsible for, and must meet its own costs of: (i) setting up and maintaining interfaces between its systems and the API, using suitably qualified Personnel and in accordance with the Documentation; (ii) establishing and configuring its systems for the use of the API in accordance with the Documentation; and (iii) obtaining and maintaining all hardware, software and communications equipment necessary to access and use the API. (d) The Customer must review the Documentation to ensure that its systems continue to integrate with the APIs as updated and modified by the Supplier from time to time. (e) Without limiting the obligations under clause 3.4(d), the Supplier will endeavour to provide the Customer with reasonable notice, where possible, of any material updates or modifications to the API and to the Documentation. If the Supplier makes any updates or modifications to the API or the Documentation, to the maximum extent permitted by law, the Supplier will not be liable. (f) The Customer must not (and you must ensure that Users do not): (i) access or use the API in any way that is improper or breaches any laws, infringes any person's rights (including intellectual property rights and privacy rights), or that gives rise to any civil or criminal liability; (ii) interfere with or interrupt the supply of the API, or any other person’s access to or use of the API; (iii) introduce any viruses or other malicious software code through the API; (iv) use any unauthorised or modified version of the API, including but not limited to for the purpose of building similar or competitive software or for the purpose of obtaining unauthorised access to the API; (v) attempt to access any data or log into any server or account that the Customer is not expressly authorised to access; (vi) circumvent user authentication or security of any of our networks, accounts or hosts or those of any third party; or (vii) access or use the API to transmit, publish or communicate material that is, defamatory, offensive, abusive, indecent, menacing, harassing or unwanted.
API Licence. 2.1. The Client’s use of the API and any content made available to the Client through use of the API (API Content) (including use of the API through a third party application that uses the API) is subject to compliance with these Terms. AroFlo grants to the Client a non-transferrable, non-exclusive, revocable licence (without the right to sublicense) to: (a) use the API solely as necessary to develop, test, operate and support the Client’s App using certain API Content accessed via the API; and (b) distribute or allow access, including for a fee, to the Client’s integration of the API within the App to end users of the App (the Licence). You may not sell, rent or redistribute access to the API or any API Content to any third party without AroFlo’s prior written approval. 2.2. To access the API in accordance with the Licence, the Client must have an AroFlo account or be granted access via a user log-in to an AroFlo customer account (AroFlo Account). The Client may create applications for which it will receive access credentials (Access Credentials). The Client should keep its Access Credentials secure and confidential as it will be solely responsible for any activities occurring in relation to the Access Credentials or via the API in the AroFlo Account. 2.3. An AroFlo customer or Client may request multiple Access Credentials but AroFlo may prevent access to the API via the AroFlo Account if the AroFlo customer or the Client: 2.3.1. has opened an excessive number of them; 2.3.2. has created multiple Access Credentials to bypass API Technical Limits (described below) or restrictions. 2.4. If a Client’s Access Credentials are suspended, the Client must not attempt to circumvent such suspension by registering for new Access Credentials. A Client may not request Access Credentials if the Client is a competitor of AroFlo. 2.5. If AroFlo issues a token that permits the Client’s App to access or modify data in an AroFlo user’s account (Access Token), the Client can only use that Access Token with that specific App and cannot use that Access Token with any other application. The Client must not sell, trade or give an Access Token to any third party without AroFlo’s prior written consent. The Client must take reasonable measures to safeguard Access Tokens and Access Credentials from unauthorised use or access. 2.6. The Client is responsible for determining: (a) who will be a User of the API; and (b) whether any User should have access to the API revoked at any time ...
API Licence. 4.1 In consideration of the Charges, WhenFresh grants to the Customer a non- exclusive licence to use the API 4.2 In relation to scope of use: 4.2.1 for the purposes of clause 4, use of the API shall be restricted to use of the API in for the purpose of ordering Data (which shall not include allowing the use of the API by, or for the benefit of, any person other than an employee of the Customer), or as permitted on the Term Sheet; 4.2.2 the Customer may not use the API other than as specified in clause 4 and clause 4.2.1 without the prior written consent of WhenFresh, and the Customer acknowledges that additional fees may be payable on any change of use approved by WhenFresh; 4.2.3 the Customer may make as many backup copies of the API as may be necessary for its lawful use. The Customer shall record the number and location of all copies of the API and take steps to prevent unauthorised copying; 4.2.4 except as expressly stated in this clause 4, the Customer has no right (and shall not permit any third party) to copy, adapt, reverse engineer, decompile, disassemble, modify, adapt or make error corrections to the SDK in whole or in part except to the extent that any reduction of the API to human readable form (whether by reverse engineering, decompilation or disassembly) is necessary for the purposes of integrating the operation of the API with the operation of other software or systems used by the Customer, unless WhenFresh is prepared to carry out such action at a reasonable commercial fee or has provided the information necessary to achieve such integration within a reasonable period, and the Customer shall request WhenFresh to carry out such action or to provide such information (and shall meet WhenFresh's reasonable costs in providing that information) before undertaking any such reduction; 4.3 The Customer may not use any such information provided by WhenFresh or obtained by the Customer during any such reduction permitted under clause 4.2.4 to create any software whose expression is substantially similar to that of the API nor use such information in any manner which would be restricted by any copyright subsisting in it. 4.4 The Customer shall not: 4.4.1 sub-license, assign or novate the benefit or burden of this licence in whole or in part; 4.4.2 allow the API to become the subject of any charge, lien or encumbrance; and 4.4.3 deal in any other manner with any or all of its rights and obligations under this Agreement, without the prior written conse...
API Licence. 2.1 Subject to the terms of this Addendum, MarketAxess hereby grants to the Subscriber a non-exclusive, non-transferable, non- sublicensable (save in respect to Permitted Affiliates in accordance with Clause 8 of the Master Agreement), revocable and limited licence during the Term to use the API solely to interact with the Systems in order to receive the Services. 2.2 Except as otherwise provided for under this Addendum, Subscriber will not, and will not permit any person under its control (including Authorised Users) to, (i) tamper with, adapt, reverse engineer, translate, decompile, disassemble, modify, copy, disseminate or otherwise dispose of the API, in whole or in part; (ii) create any upgrades or other translations, adaptation, variation, modifications or enhancements to the API; (iii) rent, lease, or transfer any part of the API to any person or entity (other than to third party developers pursuant to paragraph 4.3 below) without the prior written consent of MarketAxess; (iv) sublicense, assign, delegate or otherwise transfer (other than to Permitted Affiliates and third party developers pursuant to paragraph 4.3 below) the license granted to Subscriber under this Addendum, or the API or any of the related rights or obligations either under this Addendum or in the API for any reason; (v) attempt to download, connect, gain or provide access to or use the API for any purpose not expressly authorised by this Addendum or the Master Agreement; (vi) use the Dashboard Data, Reference Data and any other data received via the API for any purposes other than in accordance with the Master Agreement and, if applicable the Addendum for Data by way of Feed; during the Term. 2.3 The Subscriber agrees that it shall not allow access the API to any third party, including, without limitation, to any of its Affiliates (including Permitted Affiliates) or Delegated Recipients without the prior written consent of MarketAxess. 2.4 Except as expressly granted herein, nothing in this Addendum grants the Subscriber any additional rights (including Intellectual Property Rights) other than those set out in Master Agreement. MarketAxess, its Affiliates, and its applicable licensors shall retain all Intellectual Property Rights in and to the API and the Services.

Related to API Licence

  • Licence You must ensure that you hold all necessary licences, permits and approvals that are required by Law (including a Dairy Industry Licence) in order to comply with your obligations under this Contract. Failure to comply with the obligations under this clause may result in DFMC suspending the collection of your milk until such time as the failure is rectified.

  • Software Licensing Contractor represents and warrants that the software, if any, as delivered to City, does not contain any program code, virus, worm, trap door, back door, time or clock that would erase data or programming or otherwise cause the software to become inoperable, inaccessible, or incapable of being used in accordance with its user manuals, either automatically, upon the occurrence of licensor-selected conditions or manually on command. Contractor further represents and warrants that all third party software, delivered to City or used by Contractor in the performance of the Contract, is fully licensed by the appropriate licensor.

  • Licences 4.1 Lonza hereby grants to Licensee a world-wide non-exclusive licence (with the right to sublicense, subject to Clause 4.3 below) under the System Know-How and Patent Rights to use, develop, manufacture, market, sell, offer for sale, distribute, import and export Product in the Territory. 4.2 Save as expressly provided by Clause 2.2 above, the Licensee hereby undertakes not to make any modifications or adaptations to the System during the subsistence of this Agreement. 4.3 Subject to the provisions of this Clause 4.3, Licensee shall be entitled to grant a sublicence to the rights granted by Clause 4.1 to any one or more third parties for the purposes of any such third party producing Product for Licensee provided always: 4.3.1 Licensee shall ensure such sublicensee’s use of the System, the Intellectual Property and the Product is undertaken solely for the purpose of establishing a manufacturing process for Product, or producing Product, for Licensee; and 4.3.2 The sublicensee shall not, by virtue of this Agreement, be granted any right or licence, either express or implied, under any patent or proprietary right vested in Lonza or otherwise, to use the System, the Intellectual Property or the Product other than for the purposes of establishing a manufacturing Process for Product or producing Product for Licensee and Licensee agrees to ensure that such sublicensee shall not assign, transfer, further sublicense or otherwise make over the benefit or the burden of the rights granted to it pursuant to this Agreement; and 4.3.3 Any sublicence granted shall be expressly subject and subordinate to the terms of this Agreement, and it shall be Licensee’s responsibility to ensure the strict adherence by any sublicensee hereunder to the terms and conditions of this Agreement; and 4.3.4 Prior to the grant of any sublicence pursuant to this Clause 4 Licensee shall obtain the written consent of Lonza (such consent not to be unreasonably withheld), to the grant of such sublicence. 4.4 If, on a country-by-country basis, any granted patents that form part of the Patent Rights (including any re-issued patents and unexpired patents), subsequently expire or no longer contain a Valid Claim such Patent Rights shall automatically fall outside the scope of this Agreement and the provisions of Clauses 4.1 to 4.3 shall only apply, with respect to granted patents, to those granted patents which contain a Valid Claim and form part of the Patents Rights for as long as those granted patents remain in force. 4.5 On a country-by-country basis, where no Valid Claims within the Patent Rights remain in force, the provisions of Clauses 4.1 to 4.3 shall only apply for as long as the System Know-How remains secret and substantial.