API Access Clause Samples

API Access. 12.2.1 Delegate will make available to Pledgor and Secured Party, through an application programming interface, near real time, read-only information with respect to the Custodial Account, including the amount of Collateral in the Custodial Account and information with respect to deposits and withdrawals (“API”). Pledgor hereby authorizes and consents to Delegate providing such API and the API Information (as defined below) to the Secured Party with respect to the Custodial Account. 12.2.2 By accessing the API, Pledgor and Secured Party agree that: (a) The API is being provided on an “as is” basis for its internal use only and only by users that are authorized by Pledgor or Secured Party (“Authorized Individuals”) shall access the API; (b) each of Pledgor and Secured Party shall, and shall cause each Authorized Individual to, access the API exclusively through a secure point including, but not limited to graphical or programmatic interfaces, whether accessed via the Internet, a private connection or any other technological means, using unique login credentials assigned to each Authorized Individual; (c) each of Secured Party and Pledgor assumes all risk and bears sole responsibility for establishing access to the API; (d) All information provided via the API (the “API Information”) is and shall remain the sole and exclusive property of Delegate; (e) each of Pledgor and Secured Party shall have no right to use the API Information except as expressly permitted by the Agreement; (f) distribution of API Information is expressly prohibited; (g) Delegate may deny Secured Party’s or Pledgor’s access to the API at any time and without notice, for any reason including, but not limited to Delegate’s belief that such access is in violation of this Agreement; (h) each of Pledgor and Secured Party shall be responsible for all acts or omissions of any person utilizing the API through its access; (i) Delegate has no responsibility for transmissions that are inaccurate or not received by Delegate; and (j) Delegate makes no warranty, express or implied, concerning the API or with respect to any data or information made available through the API and Delegate expressly disclaims any implied warranties of merchantability or fitness for a particular purpose, including any warranty for the use of the API with respect to its correctness, quality, accuracy, completeness, reliability, performance, timeliness, continued availability or otherwise. Each of Secured Party’s and ▇▇▇▇▇▇▇...

API Access. Customer may access the ClearGov API to distribute and display public-facing content from the ClearGov Apps within one or more Customer Web Site(s).

API Access. (A) Most Services are provided through ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/ or any associated websites or application programming interfaces (“APIs”) (collectively, the “Company Site”). Client may elect to utilize the APIs either directly or indirectly within an independently developed application (“Developer Application”). (B) All API-based services are subject to usage limits. If Client exceeds a usage limit, Trust Company may provide assistance to seek to reduce Client usage so that it conforms to that limit. If Client is unable or unwilling to abide by the usage limits, Client will order additional quantities of the applicable Services promptly upon request or pay Trust Company’s invoices for excess usage.

API Access. Subject to the terms and conditions of this Agreement and Box’s fair use policy, Customer shall have a non-exclusive right during the applicable Subscription Period to incorporate the API into any Platform Application or application used by or on behalf of Customer for the sole purpose of accessing the Box Service or accessing certain functionality of the Box Service, provided that such access is limited to the amount provided with Customer’s subscription level plan plus any API call allotments purchased by Customer in the applicable Order and Section 2.2 below.

API Access. (A) Most Services are provided through ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/ or any associated websites or application programming interfaces (“APIs”) (collectively, the “Company Site”). Client may elect to utilize the APIs either directly or indirectly within an independently developed application (“Developer Application”). (B) All API-based Services are subject to the terms and conditions set forth at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/legal/services-agreement (the “API Terms”), as they may be amended from time to time. In the event of a conflict between the API Terms and the terms of this Agreement, the terms of this Agreement shall control. If Client exceeds a usage limit, Custodian will use commercially reasonable efforts to provide notice to Client (and may provide notice if Client is likely to exceed such limit) and may provide assistance to seek to reduce Client usage so that it conforms to that limit. If Client is unable or unwilling to abide by the usage limits, Client will reasonably negotiate to enter into order forms for additional quantities of the applicable Services promptly or pay Custodian’s invoices for excess usage based upon BitGo’s then-current standard rates.

API Access. If available in purchased edition, Novo grants Customer a non-exclusive terminable license to interact with the Novo application-programming interface (API) only in conjunction with its use of the Service. Customer may not reverse engineer the API, or excessively use or access the API. The API is provided on an AS IS and AS AVAILABLE basis. Novo may temporarily suspend the API without notice, and change or terminate Customer’s API license upon at least 30 days advance notice to the email address in Customer’s account. Novo is not liable for any cost, loss or damage sustained by Customer as a result of any suspension, change or termination of API license.

API Access. Subject to the terms and conditions of this Agreement and Box’s fair use policy, Customer shall have a non-exclusive right during the applicable Subscription Period to incorporate the API into any Platform Application or application used by or on behalf of Customer for the sole purpose of accessing the Box Service or accessing certain functionality of the Box Service, provided that such access is limited to the amount provided with Customer’s subscription level plan plus any API call allotments purchased by Customer in the applicable Order and Section 2.2 below. 2.1(C) Overages. During the Subscription Period, Box may provide Customer with a report identifying the number of Users (or API calls, bandwidth or other tolled usage, if applicable) that, at any time, exceeds Customer's usage limits, and Box (or Box Reseller, if applicable) may provide Customer with an Order to purchase for the additional Box products for ongoing use (“Expansion Service Order”). Customer shall promptly (but in any event within thirty (30) days of receiving such Expansion Service Order) either: (i) execute the Expansion Service Order; or (ii) increase the usage limit through an alternate purchase method provided by Box (e.g. the “Add Seats” function in the Administrative Console, if available to Customer); or (iii) permanently delete the excess Accounts or other applicable activity. れ、本顧客のサブスクリプションレベルプランに対応する利用限度に従ってのみ、Box サービスを利用することができる。管理者により管理されていない場合であっても、管理対象ユーザーのアカウント、および本顧客の管理者により実行、開設され、あるいは直接管理されている外部ユーザーに対するアカウントは、 各々本顧客の利用限度（アカウントライセンスあるいはシートを呼ばれることもある）に加算される。Boxは、利用限度を超えて本顧客が Box サービスを利用、または追加のアカウントを実行することを制限することができる。 2.1

API Access. Every type of account communicates with HEROES through APIs (on top of which interfaces can be developed – e.g., web portal). It is needed for many use cases, for example for our services in the cloud / HPC centres to report back to the HEROES solution on certain events (e.g., end of job…) or to report metrics. As most HPC Centres will not allow to have outgoing network connections, we will rely mainly on a “pull model” to gather information about running jobs or accessing data: the HEROES platform will contact, through SSH, the HPC Centre to execute commands, gather information, for all its interaction with the Centre. The API access to HEROES platform will mainly be for third party tools, or between HEROES modules.

API Access. In the event we provide a Data Set via an API, you may use the applicable API solely to access and use the applicable Data Set as set forth herein. In addition, you shall not (and shall not authorize or knowingly permit any third party to) make any use or disclosure of the APIs that is not expressly permitted under this ▇▇▇▇. Without limiting the foregoing, you shall not (and shall not authorize or knowingly permit any third party to): (i) reverse engineer, decompile, disassemble, or otherwise attempt to discern the source code or interface protocols of the APIs; (ii) modify, adapt, or translate the APIs; (iii) resell, distribute, or sublicense the APIs or otherwise allow any third party to use or access the APIs; (iv) remove or modify any proprietary marking or restrictive legends placed on the APIs; (v) use the APIs in violation of any Applicable Laws (as defined below) or for any purpose not specifically permitted in this ▇▇▇▇;