API Integrations Sample Clauses
API Integrations. In exchange for a *** paid by AT&T to Motricity, Motricity shall support 10 standard API integrations over a twelve (12) month span, which includes current projects Media Net 4 and Media Mall. Notwithstanding the foregoing, Motricity shall waive the *** fee for each month in which Total Gross Revenue through the client API exceeds *** Motricity shall invoice any such fees monthly in arrears. Although payment is recurring and will be made monthly starting when this amendment is signed, if an API integration is delayed due to fault of Motricity, the monthly fee would be reduced proportionally (example - if Motricity can support 3 integrations concurrently and one is delayed due to Motricity fault, the monthly fee would be reduced by one third for that month, and subsequent months, until corrected). A project plan will be mutually agreed upon by Motricity, the client application provider, and AT&T at the start of each new API integration project. Motricity will be subject to NPCs upon failure to meet the committed number of standard integrations (10) for 2008. *** It is estimated that a standard API integration would take *** per integration to reach a production ready state and an additional *** per month to support. The impacts by functional area are: • *** Initial Consultation • *** Integration Support • *** Configuration The deliverables for a standard implementation are outlined in the table below: Catalog Motricity will provide access to the current Client catalog Catalog Maintenance Motricity will provide ongoing maintenance to the Client catalog to ensure fresh content Integration Kickoff Motricity will chair a kick-off meeting via conference call for each integration. Integration Support Motricity will provide integration support for each integration via email. In-life Support Motricity will provide in-life technical support for each integration for a period of 2 years past execution of the SOW Upgrade Path Motricity will provide a smooth upgrade path for each integration for a period of 2 years past execution of the SOW Documentation Motricity will provide all relevant API documentation Production Support The production APIs will be monitored 24x7x365 via Motricity NOC personnel The following items are assumptions, dependencies & risks associated with the AT&T Standard Client API Integrations: • As part of a standard integration, support will only cover API specific questions, not application specific questions. • Standard Integration fees apply onl...
API Integrations. Payment gateway services are provided by Lynnbrook. Integration with other gateway service provides will require an additional fee as established by Company.
API Integrations. 15.1 By signing a quotation for an API between the Client’s GoodX and API Third Party Software, the Client grants GoodX and the API Third Party the following permission:
15.1.1 The Client consents to the API integration between the GoodX software licensed to the Client and the Third Party software for the benefit of the Client;
15.1.2 The Client grants permission that the API Third Party Software may import/export data into/from the GoodX Software of the Client.
15.2 GoodX undertakes to provide the API Third Party with the necessary integration details to complete the integration.
15.3 Each party to the API shall furnish the other with 30 days' notice of any intention to alter any material element of the integration to give the other party ample time to alter their software so that no interruption of services will negatively impact the Client’s business.
15.4 If any party fails to comply with this agreement, the other party may terminate the API agreement by giving 7 days' notice of its intention to cancel the agreement.
15.5 The Client and API Third Party acknowledge that the integration is done solely at the client's risk.
15.6 GoodX shall not be held liable for any Imported Business Information that may be damaged or lost due to data being imported into the GoodX Software and database from the API Third Party Software via the API.
15.7 The Client undertakes to ensure that the data imported into the GoodX Software is correct and will, at its own expense, make changes to the data if data is not correctly imported into the GoodX Software and database.
15.8 GoodX shall not be liable, whether in contract, delict or otherwise, for any direct, indirect, special or consequential loss or damage or any loss of profit suffered or sustained by the Client as a result of or in connection with the API or reliance on incorrect data provided by the API Third Party Software.
API Integrations a. As part of the Services, you may be granted a limited, non-exclusive, non-transferable, revocable license to use our API key.
b. You are solely responsible for the quality and accuracy of the data you upload to Badger using the API key. If there are repeated mistakes in the data uploaded, ▇▇▇▇▇▇ may deny your right to upload data.
c. Requests to Badger through the API key are limited to 25,000 requests per day per team. Requests to Badger through the API exceeding this amount may result in temporary or permanent suspension of your account’s access to the API. In our sole discretion, we may determine the abuse or overuse of the API, and we will make a reasonable attempt to warn you by email before suspension.
d. It is your responsibility to respect the privacy of your users per your privacy policy and to implement and maintain appropriate technical and organizational security measures to protect and preserve the security, integrity, and confidentiality of your user’s data when using our API keys.
e. You are prohibited from using the API key for spamming or taking any other action that violates this Agreement.
f. Your use of the API key is monitored for compliance with these rules, and we may decide in our sole discretion to deny your access to the API if you violate this policy.
API Integrations. ○ Secure RESTful APIs for interoperability with third-party platforms such as trip planning, dispatch systems, and external databases. ○ Middleware for seamless data synchronization and service updates.
API Integrations. This use case is best represented around Petco park. We envision connecting just 2-3 segments to the cloud, so we can program an API feed to the MLB, in which case we can have the lights dance when a homerun is registered in the MLB gamecast. This same concept may be applied to other critical locations that could benefit from user engagement. For example if you would like for artistic expression on one block that would allow pedestrians to change the lights.