API Integration Clause Samples
The API Integration clause defines the terms and conditions under which two or more software systems will connect and interact via their respective application programming interfaces (APIs). It typically outlines the technical requirements, responsibilities for maintaining compatibility, and any limitations on data exchange or usage between the integrated systems. This clause ensures that both parties understand their obligations regarding the integration, helping to prevent misunderstandings and technical disputes by clearly specifying how the systems will work together.
POPULAR SAMPLE Copied 47 times
API Integration. Subject to the terms of the applicable Order Form, Section 4.2 above (including the limitations described in Schedule 1 hereto), and the Master Subscription Agreement under which Customer has purchased SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM subscriptions, Customer may access SFDC APIs for the purposes of accessing, interacting with and/or querying D&B Data for use in applications, business logic and workflows associated with Customer’s org for SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM, or with AppExchange offerings.
API Integration. The Company may provide application program interfaces (API) for mission critical functions. Support and consulting fees shall be based on Your integration requirements. Termination of this agreement will cancel and deactivate all API integration with the Person Trust network. The Company may obtain a license to offer and implement 3rd party API’s from our vendor partners. The Company does not warranty or excepts any responsibility or liability for any 3rd party API, integration, functionality, or security. Neither of us shall be responsible for failure or delay of performance if caused by an act of war, hostility, or sabotage; act of God; electrical, internet, or telecommunication outage that is not caused by the obligated party; government restrictions (including the denial or cancellation of any export or other subscription); other event outside the reasonable control of the obligated party. We both will use reasonable efforts to mitigate the effect of a force majeure event. If such event continues for more than thirty (30) days, either of us may cancel unperformed services upon written notice and You will only be required to any fees up to the date of termination and will not be charged any penalties or required to pay any other fees. This section does not excuse either party’s obligation to take reasonable steps to follow normal disaster recovery procedures, the Company’s obligation in the event of a breach of any of the provisions of the Nondisclosure requirements herein, or Your obligation to pay for programs delivered or services provided herein described.
API Integration. Access to or use of the ClubReady API platform (“ClubReady APIs”) will be subject to ClubReady’s API Terms of Use. If you access Third Party Services through the ClubReady APIs, we reserve the right to charge you a monthly API Use Fee as described in the Service Order.
API Integration. The Company may provide application program interfaces (API) for mission critical functions. Support and consulting fees shall be based on Your integration requirements. Termination of this agreement will cancel and deactivate all API integration with Persona Trust™ service. The Company may obtain a license to offer and implement third-party API's from our vendor partners. The Company does not warranty or excepts any responsibility or liability for any third- party API, integration, functionality, or security. PERSONA TRUST TM Services anticipates one hundred percent (100%) connectivity for all identity proofing transactions. If connectivity interruption occurs PERSONA TRUST TM Services will reasonably execute best practices to restore connectivity including telephone or email contact of Your client, to complete the identity proofing transaction.
API Integration. If resources are available, the JMS provider can create a web service on their end. Edovo/Legacy will provide API documentation to facilitate this process. The API interface enables opening and closing accounts, PIN updates, Resident Identifier updates, name changes, deposits, and balance updates, closing accounts, releasing refunds, and location updates. The API interface is available in both standard SOAP and RESTful platforms and is compatible with XML Version 1.0 and utf-8 encoding. Alternatively, the JMS provider’s API can also be called if the appropriate documentation is provided.
API Integration. Vendor is required to consume Comcast and Third Party Vendor API functionality, within **** of functionality becoming production ready or at a Comcast defined date, whichever is later. This functionality will be integrated into the Vendor CRM and be used during all relevant chat and call transactions by Vendor agents. **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
API Integration. Subject to the terms of the applicable Order Form, Section 4.1 above, and the Master Subscription Agreement under which Customer has purchased SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM subscriptions, Customer may access SFDC APIs for the purposes of accessing, interacting with and/or querying D&B Data for use in applications, business logic and workflows associated with Customer’s org for SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM, or with AppExchange offerings. 5. D&B DATA DELETION AND POST-TERM LICENSE
5.1. Offline ▇▇▇▇.▇▇▇ Services. Except as otherwise expressly permitted in a ▇▇▇▇.▇▇▇ Order Form, upon termination or expiration of any offline ▇▇▇▇.▇▇▇ Service subscription hereunder, Customer shall delete or destroy all copies of D&B Data in its systems, or otherwise in its possession or control, that Customer acquired pursuant to such terminated or expired subscription. Upon written request by SFDC, Customer shall provide written documentation to SFDC evidencing any deletion required under this paragraph.
API Integration. The Medipass Solution uses standardised interfaces which enable quick integrations, whilst retaining key systems of record and minimising impact to group wide financial reporting, accounting and management reporting.
(a) Product / Service
API Integration. Botlink will allow users to define a relationship and transfer stitched images from a Mission in the Botlink platform to pre-defined third party systems.
API Integration. Subject to the terms of the applicable Order Form, Section 4.2 above (including the limitations described in Schedule 1 hereto), and the Main Services Agreement under which Customer has purchased SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM subscriptions, Customer may access SFDC APIs for the purposes of accessing, interacting with and/or querying D&B Data for use in applications, business logic and workflows associated with Customer’s org for SFDC’s ▇▇▇▇▇▇▇▇▇▇.▇▇▇ CRM, or with AppExchange offerings. 5. D&B DATA DELETION AND POST-TERM LICENSE
5.1. OFFLINE ▇▇▇▇.▇▇▇ SERVICES. Except as otherwise expressly permitted in an Order Form for the purchase of ▇▇▇▇.▇▇▇ Services, upon termination or expiration of any offline ▇▇▇▇.▇▇▇ Service subscription hereunder, Customer shall delete or destroy all copies of D&B Data in its systems, or otherwise in its possession or control, that Customer acquired pursuant to such terminated or expired subscription. Upon written request by SFDC, Customer shall provide written documentation to SFDC evidencing any deletion required under this paragraph.
