API Sample Clauses

API. If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.
AutoNDA by SimpleDocs
API. I agree to access my RHC Account only through the Robinhood Platform. Any other use is not authorized and I agree to refrain from using any application programing interface belonging to RHC or any of its Affiliates.
API. A. Reliant shall supply to Cardinal Health for Manufacturing and Packaging, at Reliant’s sole cost, the API and applicable reference standards in quantities sufficient to meet Reliant’s requirements for each Product as further set forth in Article 4. Prior to delivery of any of the API or reference standard to Cardinal Health for Manufacturing and Packaging, Reliant shall provide to Cardinal Health a copy of the API Material Safety Data Sheet (“MSDS”), as amended, and any subsequent revisions thereto. Reliant shall supply the API, reference standards, and Certificate of Analysis FOB the Facility no later than thirty (30) days before the scheduled Manufacture Date upon which such API will be used by Cardinal Health. Upon receipt of the API, Cardinal Health shall conduct identification testing of the API. Cardinal Health shall use the API solely and exclusively for Manufacturing and Packaging under this Agreement. The maximum volume of API that Reliant supplies to Cardinal Health shall not exceed the amount reflected in the Firm Commitment and the next six (6) months of the Rolling Forecast.
API. If supported by your plan, authorised users and administrators may be able access their account via an API. Authorised users and administrators must not abuse the API specifications. Any abuse or misuse of the API may lead to suspension or termination of the services. • Where you access your account via an API, you are responsible for meeting and complying with the API specifications. • We may change or republish the API specifications for any service from time to time. It is your responsibility to ensure that the application calls made to a service are compatible with then current APIs for that service. If we remove a material feature or function of the API, we will provide you with at least 30 calendar days written notice and will ensure that backward compatibility with any previously valid APIs is maintained for a period of 90 calendar days. Thereafter, we may remove the previously valid APIs. You must make changes to your systems, at your expense, which may be necessary to comply with the amended API specifications.
API. If GSK fails to manufacture, have manufactured, test, store, or release any API sold to Prometheus in accordance with the Specifications, cGMPs, Applicable Laws, and Regulatory Acts, then (i) GSK shall reimburse or credit Prometheus the price paid by Prometheus to GSK for the affected API under the original invoice for such affected API, including any freight, taxes, duties and insurance charges paid; and (ii) GSK shall reimburse or credit Prometheus for the actual costs incurred, directly or indirectly, in shipping, insurance premiums, duties, taxes paid or any other out-of-pocket charges incurred in connection with collection, transportation and return or destruction of the affected API. Prometheus shall provide GSK with such information and documentation as GSK may reasonably request to confirm any of the foregoing charges, costs or expenses. For the avoidance of doubt, any replacement of API is subject to the limitations of Section 4.4(a) and 4.4(b).
API. RB shall timely provide MSX with all necessary API free of charge. In the event that RB fails to provide API meeting the API Specification in a timely manner and MSX can demonstrate that such failure caused delays in MSX’s ability to perform its obligations under this Addendum and MSX notifies RB of such delays in writing at the time such delays are occurring, then MSX may deduct the amount of time its performance of a particular milestone activity was delayed by such failure from the total amount of time MSX took to complete a particular milestone activity for purposes of determining whether MSX receives a bonus or penalty for its performance of the particular milestone under Appendix A. Failure of RB to timely deliver API or at all shall not be used by RB as grounds to avoid its obligation to make any milestone payment provided for in this Addendum.
API. If the Service offers integration capabilities via an API, your use of the API may be subject to additional costs, Sage specific policies, and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Service, or in contravention of any applicable laws. We reserve the right in our sole discretion to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you.
AutoNDA by SimpleDocs
API. The Product(s) may include one or more application program interfaces (“API(s)”) that allow Customer to develop applications, code or services that communicate with the Product (collectively, “Customer Applications”). Such APIs, if any, may be available upon request. Customer may use an API only if such use is authorized in the Documentation or otherwise in writing by Trimble. Use of APIs may be subject to additional terms and conditions. Trimble may modify APIs from time to time, and Trimble is not responsible for the compatibility of any such modifications with Customer Applications.
API. API I and API II each represent and warrant to DTR:
API. In the event that either party is able to secure a lower price for the API from a source that meets Noven's quality requirements, subject to Noven's contractual commitments with its suppliers, Noven will work with Endo in good faith to utilize such API in place of its own source of API. Once agreed to by both parties to qualify a lower price API, Endo and Noven shall equally share all out of pocket expenses in qualifying and otherwise securing such new API source. To the extent that Noven is able to use such lower priced API, the lower cost will be reflected in Noven's manufacturing costs for the Product. *** In the period prior to commercial launch of the Product, to the extent that Endo supplies Noven with the API, Endo will invoice Noven for the portion of the cost of such API for which Noven is assuming risk pursuant to Section 3.09 below. All such invoices shall be due and payable within thirty days of receipt and shall bear interest at the rate of 1% per month or the maximum allowable by law on any overdue amounts. Noven shall include such API costs in its manufacturing costs and Endo shall deduct the API costs not invoiced to Noven from the next *** payment otherwise owed Noven under the License Agreement. After the commercial launch of the Product, Endo shall deduct the cost of the API it supplies Noven from the next *** payment otherwise owed Noven under the License Agreement.
Time is Money Join Law Insider Premium to draft better contracts faster.