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. 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. 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. 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.
