API Calls Clause Samples

API Calls. If Partner exceeds the number of API Calls allocated as part of the Services, Flare reserves the right to charge overage Fees as specified in the Partner Portal, or in a Purchase Order. Continued access to the Flare APIs may be suspended until such overage Fees are paid.

API Calls. Red Hat reserves the right to suspend the Online Service if your API Call volume exceeds the maximum limits of fifty million (50,000,000) per day, thirty thousand (30,000) per minute or one thousand (1,000) per second, unless otherwise agreed by the parties in writing. There is no limit on the number of environments and locations where you may deploy API management agents.

API Calls. Section 2.4.6 of the Agreement is amended by replacing the words “calendar quarter prior to the Effective Date” in the fourth and seventh sentences with the words “the second calendar quarter of 2010.” Yahoo! represents that the Historical Call Rate during the second calendar quarter of 2010 is consistent with Yahoo!’s past practices (including those of the calendar quarter prior to the Effective Date) and that Yahoo! did not materially change the Historical Call Rate after the Effective Date.

API Calls. For each Query from any of the Yahoo! Properties and Syndication Properties, Yahoo! will submit one or more calls to the Microsoft API indicating the number of Paid Listings and Algorithmic Listings requested by Yahoo! for each aspect of the Services (e.g., Web, image, Paid Listings) and Microsoft shall return such number of Results for each such Service (or all Results if the amount requested is not available) in accordance with the terms of this Agreement. Yahoo! will not serve any cached Results previously delivered by Microsoft unless the parties otherwise mutually agree in writing. Microsoft will implement a mechanism for Yahoo! to specify via the Microsoft API (or some other mechanism) which calls to the Microsoft API are multiple calls for the same Query, and Yahoo! will use such mechanism to designate which calls are secondary calls (i.e. those in addition to the first call) when submitting multiple calls for the same Query. Within 30 days after the Effective Date, Yahoo! will provide Microsoft with the number of calls made to its own Algorithmic Search Services (excluding calls which are not made in response to a Query such as test calls), in each country and the number of corresponding Queries in each country as measured over the calendar quarter prior to the Effective Date. The total number of calls made by Yahoo! and the Syndication Partners to the Yahoo! Algorithmic Search Services during such period in each country divided by the corresponding Queries during such period in each country will be the “Historical Multiple Call Rate” for that country (e.g., if Yahoo! and the Syndication Partners made 300 calls for 150 Queries during the period the Historical Multiple Call Rate [*] Indicates that certain information in this exhibit has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to omitted portions.

API Calls. For each Mobile Query from any of the Yahoo! Mobile Properties and Mobile Syndication Properties, Yahoo! will have the right to submit separate calls to each component of the Microsoft Mobile APIs for Mobile Algorithmic Listings (including a single call requesting one or multiple content categories) and Mobile Paid Listings and otherwise in accordance with Section 2.4.6.

API Calls. API calls are made when you access Lendysoft through its API or when you access Bricknode Financial Systems “BFS” through the BFS API. Bricknode and Lendysoft will calculate the number of calls made by you and can be associated with fees according to our current price list.

API Calls. For each Query from any of the Yahoo! Properties and Syndication Properties, (i) Yahoo! will submit a single call to the Microsoft API (unless the parties subsequently agree, acting reasonably, that separate calls are appropriate) indicating the number of Paid Listings and Algorithmic Listings requested by Yahoo! and Microsoft shall return such number of Results (or all Results if the amount requested is not available) in accordance with the terms of the Search Agreement and (ii) Yahoo! will not serve any cached Results delivered by Microsoft. If Yahoo! does not display all of the Results (as permitted in the Search Agreement), then Yahoo! will subsequently, in a form, manner, and timing to be agreed, deliver a report or data feed describing which Results were not displayed, any modifications to the ordering or display of the Results, or any additional content included with the Results. For clarity, the immediately previous sentence does not grant Yahoo! any additional rights; rather, the previous sentence is intended to provide Microsoft with visibility into these activities as authorized elsewhere hereunder. i) Yahoo! may conduct test Queries requesting over [*] results on an offline basis (with relaxed SLAs). Such test Queries shall not exceed [*] Queries per second and Yahoo! will use reasonable efforts to conduct such test Queries during off-peak hours (as mutually defined by the parties). Yahoo! shall reimburse Microsoft for the Covered Marginal Costs of serving such test Queries in excess of such amount. Such test Queries shall use the same means that Microsoft uses internally for its own similar test Queries.