Application Programming Interface. Delinea will endeavor to provide an API for certain of its software products, subject to licensing capabilities, for Customer’s use solely for the purpose of creating software that communicates with the Delinea software product. Customer may create, distribute, sell, lease, rent and distribute any software it creates that utilizes the API, subject to any applicable or required licensing terms and conditions, provided the software is a non-derivative work, is solely for the Customer’s internal business purpose and the Customer does not sell a product that competes with Delinea.
Application Programming Interface. Upon Client’s request, TotalSource will provide Client with access to its Application Programming Interface services described in Part 2 of the Pricing Addendum (“API”). Client’s use of API shall be subject to the fees and costs set forth in the Pricing Addendum and shall be invoiced to Client in addition to the Service Fee described in Part 2, Section 2.A.
Application Programming Interface. In the event Client elects to use API then in addition to the terms set forth in this Agreement, the provisions provided in this Part 2, Section 8 shall apply.
Application Programming Interface. (API) – the interface(s) provided by Us to you (and the Platform to provide information and instructions on your behalf).
Application Programming Interface. Vendor documentation on application programming interface must include a listing of all data types, functional specifications, a detailed explanation on how to use the Vendor’s application programming interface and tutorials. The tutorials must include working sample code.
Application Programming Interface. This section does not apply if your Organization does not request access to eTapestry’s application programming interface, which is an interface to push data to, or pull data from, an eTapestry database (the “API”). The API may only be licensed to your Organization upon submission of an application along with any requested information and receipt of eTapestry’s approval, which may be granted or denied in eTapestry’s sole discretion. If eTapestry provides your Organization with access to the API, it will deemed to be included in the “Database Services” for purposes of this Agreement, except that any consulting services, support or other assistance requested by your Organization relating to the API are not included in any Fees specified in the Proposal unless expressly stated therein. eTapestry may limit the amount of data that may be transferred by your Organization through the use of the API, the number of concurrent sessions that your Organization may establish with the API, and/or any other activity with respect to the API, in its sole discretion and may change such limitations from time to time. eTapestry also reserves the right to terminate your Organization’s license to use the API at any time after such license is granted if eTapestry believes your Organization is using the API in an inappropriate manner. The API shall be treated by your Organization as confidential information of eTapestry. If your Organization engages a third party to provide support to your Organization and such third party requires access to the API, your Organization shall ensure that such third party does not provide the API to anyone else and uses the API solely to provide support to your Organization. Any breach of the foregoing restrictions (or this Agreement) by such third party service provider shall be deemed a breach of this Agreement by your Organization.
Application Programming Interface. The Supplier can use Xxxxx’x selling platforms in accordance with clause 6 of the Contract. The Supplier is responsible for creating an application programming interface (API) between their and Xxxxx’x technical solutions. The Supplier will cover their own costs when setting up the API.
Application Programming Interface. Three Representational State Transfer (REST) based API calls are designed for communication between the front and back end. Since adding a user management system could discourage people from using the system as it would require all visitors to register and sign in, all interfaces are open to public without authentication. As soon as the front-end page loads, a GET call is sent to controller, requesting for the scene and question type data. To reduce the overhead in front end rendering, the HTML text of each scene that needs to be rendered is pre-computed and stored in display text in Scene table. The controller follows the user guidance procedure discussed in Section 3.2 to pick a scene and question type then returns the scene display text and question type. After the user finished composing a question, a second POST call is sent to controller, which contains the payload with the question submitted by the user. The question is verified by front-end to be consistent with the question type required by the first GET call. The controller will then create a User Response entry to store the question from the user. The controller then queries the XXXX service for an answer to the question, which the controller will store as an Answer entry in the database with from model bit turned on. Finally, the controller returns the prediction to the question and the view will highlight the answer span inside the selection area in a different color from user selection. Once the user edits or confirms the answer, the third POST call is made from front-end to either to confirm model prediction or to correct model prediction. The controller will then add user’s correction as another Answer entry with from model bit turned off. Note since the interfaces are open to public and no authentication is required, a malicious user could abuse the third POST call to change the responses from a previous user arbitrarily if the interface is not implemented with care. To resolve the potential loophole, the controller assigns each response with a unique identifier obtained by Django PBKDF2 Password Hasher [14] with input from current time stamp, scene id and a random salt in the second POST call and returns the hash with answer to user. In other words, the controller creates a password hash for each response which is hard to guess, given only the id of the scene. The id of the scene is the only piece of information public to the users. This ensures a malicious third party cannot obtain the...
Application Programming Interface. This section does not apply if your Organization does not require access to Bloomerang’s Application Programming Interface ("API"), which enables third-party software to push data to, or pull data from your Bloomerang database. The API is automatically licensed to your Organization upon activation of your Bloomerang Database Service.
Application Programming Interface. Supplier agrees to provide the NSAP Voice and Telephony Application Programming Interface Specification which contains the Application Programming Interface (API) Specifications for the APIs that exist within the NSAP for communication between the Service Applications and Platform as defined by Company's Specifications listed in Exhibit D. Supplier agrees that the scope of the API Specifications will include all Service Application to Platform communications defined for the Platform software to be delivered to Company. The API Specifications will include calling conventions and autonomous indications associated with the following areas: - ******* - ******* - ******* - ******* - ******* Supplier agrees that the API Specifications will include all Platform capabilities available in the Software, including capabilities not used at all by the ************* Application as well as unused arguments or options of capabilities that are used by the ************ Application. Supplier further agrees that the API Specifications will include the following: - ******* - ******* - ******* - ******* - ******* - ******* Upon completion of the API Specifications, Supplier agrees to make the APIs an Open Interface. The API Specifications will be delivered as per the milestone specified in Section 1.17, "SUPPLIER'S MILESTONES". Supplier agrees that Company may release the API Specifications to a third party, without Supplier's written consent, for use in developing other Service Applications on the NSAP. AT&T Proprietary (Restricted) Solely for Those Persons With a Need to Know. Use Pursuant to Company Instructions. Contract No. LLJ268E Page 19 of 30
