API Development. Aratana will use commercially reasonable efforts to develop and establish a manufacturing process for the API that is cGMP compliant and fully characterized and substantially conforms to the Specifications. The target date for completion is no later than [***], provided that Aratana could be delayed due to causes beyond Aratana’s reasonable control. In case that Aratana finds the causes of delay, Aratana should promptly notify RaQualia the causes and the Parties will negotiate and set the next target date. Aratana anticipates all development of the API will take place at Cambridge Major Laboratories (“CML”) and will be performed as generally described in [***] attached hereto as Exhibit B.
API Development. After the Effective Date identified below, Entrata will provide specifications for the APIs outlined on Exhibit A. Entrata and Developer agree to work together in good faith as reasonably necessary to facilitate the completion of the APIs for their Common Clients’ benefit. Both parties will maintain and support the APIs. The parties agree that the APIs may be updated or revised to include improvements, upgrades, or other changes as required by Entrata. The parties agree to provide each other with technical assistance as the APIs may reasonably require. All costs for software modifications to Developer’s Application shall be the exclusive obligation of Developer.
API Development. An API is a software intermediary that allows two applications to talk to each other. In the context of the Company's Flexibility Services, the API replaces the requirement for dedicated hardware to be provided to connect to a Provider’s sites in order to collect the metering data and send control requests from the central control desk. Providers are expected to develop their own interface for the API to the assets that they intend to offer to the Company. Due to the large variety of potential scenarios that can occur, ranging from a single asset such as a standalone generator through to a complex estate with multiple assets or even part of a portfolio under management by a commercial aggregator. The objective of the Provider is to establish a single point where they can aggregate the metering from all assets within a DER set along with communications to send to the Company, and are able to receive start and stop requests. It is at this point that we would expect a device such as a server to be hosting an API software program. A comprehensive guide to API set-up is available on xxx.xxxxxxxxxxxxx.xx.xx/xxxxxxxxx/000.
API Development. Replay will use its best efforts to develop and document mutually agreed upon Replay Device Software APIs reasonably necessary for the development of MKE Products that combine Replay Technology with other features and functionality developed or provided by MKE. In the event that MKE experiences significant difficulty in utilizing such APIs in connection with the development of such products, Replay will, at MKE's request, consider in good faith providing source code updates and modifications for the applicable portions of [***]= CERTAIN INFORMATION ON THIS PAGE HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. the Replay Device Software on a case-by-case basis. Any provision by Replay of such Replay Device Software source code updates and modifications shall be subject to the provisions of Section 3 hereof.
API Development. Subject to the terms of this Agreement, SB shall develop and provide: (i) a suite of APIs to query, the [**] Database (collectively, "SB APIs") and a series of tools to insert, edit and update the [**]Database, in each case as further described in Exhibit C, and (ii) other methods of data access as set forth in Exhibit C. To the extent reasonably requested by AOL, SB shall develop appropriate APIs and tools for use with the [**] Database in accordance with the terms of this Agreement.
API Development. Subject to the terms of this Agreement, AOL shall develop and provide a suite of APIs to query, insert, edit and update the [**] Database to access AOL Features or Functionality and to interoperate with the AOL YP User Interface.
API Development. Organichem shall develop the API in a timely manner and in accordance with FDA requirements, applicable requirements of the U.S. Pharmacopeia (USP), and such other specifications as shall be mutually agreed upon in writing by Organichem and Purepac.
API Development. Friendable will develop a set of network service API’s to communicate with the applications (IOS, Android, and Web) as well as CTI. API’s will be a central location for all platforms to communicate and to ensure that everything is always in sync. These include: - Architect and Design of Database table structure - Creation of approx. 30 – 40 new endpoints required (as per the API spec doc) - Device and notification management – SNS subscribe / Unsubscribe - Creation of routines to communicate changes to CTI - Create a full set of Developer Documentation - Create automated routines for task reminders, schedule changes, etc. - Bot creation or Lambda function for Log management and reporting, server cleanup, stats, admin feeds, timed events, turning off account access for past due payments, etc.
API Development. 4.6.1. An API is a software intermediary that allows two applications to talk to each other. In the context of the Company's Flexibility Services, the API replaces the requirement for dedicated hardware to be provided to connect to a Provider’s sites in order to collect metering data and send control messages.
4.6.2. Providers are expected to develop their own internet facing API endpoint and software adapter into the systems that they use in providing Flexibility Services to the Company. This is due to the variety of potential scenarios that can occur, ranging from a single asset such as a standalone generator through to a complex estate with multiple assets or even part of a portfolio under management by a commercial aggregator.
4.6.3. The Company does not provide technical integration services but may offer, at it’s discretion, a one-off “Integration Contribution” payment to the Provider of up to £5000.00 towards any integration costs incurred.
4.6.4. The Company can suggest 3rd Parties to provide integration services if requested by the Provider. The Provider is not obliged to use the suggested 3rd Party, and the Company accept no liability for the 3rd Party.
4.6.5. The Company will pay the Integration Contribution upon a successful integration test, and presentation of evidence for costs incurred (e.g. timesheets or copy of purchase order for systems integration work).
4.6.6. The Participant API specifications are published at: xxxxx://xxxxxxxxxxxxxxxxxxx.xx.xx/docs/public/index.html.
API Development. An API is a software intermediary that allows two applications to talk to each other. In the context of the Company's Flexibility Services, the API replaces the requirement for dedicated hardware to be provided to connect to a Provider’s sites in order to collect the metering data and send control requests from the central control desk. Providers are expected to develop their own interface for the API to the assets that they intend to offer to the Company. The latest definitions of each API, including the surrounding authentication are available on the Portal.
