Permitted Use; API Documentation Sample Clauses

Permitted Use; API Documentation. You may use the APIs to design and integrate one or more PrismHR products with products, websites and/or services that are offered by you (the “Product Offerings”), subject to the Terms and Conditions. PrismHR may, but is under no obligation to, make available reference materials, including API documentation, wrapper libraries, source code and/or sample code (the “API Documentation”), all which may be amended or revised by PrismHR at any time. All API Documentation is subject to the Terms and Conditions. We reserve the right to change or discontinue the availability of any or all of the PrismHR APIs and/or the API Documentation at any time at our sole and exclusive discretion.
AutoNDA by SimpleDocs

Related to Permitted Use; API Documentation

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Construction materials (1) The restrictions of section 1605 of the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5) (Recovery Act) do not apply to Recovery Act designated country manufactured construction material. The restrictions of the Buy American statute do not apply to designated country unmanufactured construction material. Consistent with U.S. obligations under international agreements, this clause implements--

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Customer a non-exclusive, non-transferable right and license to use the Documentation during the Service Term for Customer’s internal purposes in connection with its use of the Flock Services as contemplated herein.

  • Service Documentation The “Service Documentation” includes;

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

Time is Money Join Law Insider Premium to draft better contracts faster.