Integrations and API Availability Clause Samples
The "Integrations and API Availability" clause defines the terms under which a service or software provides access to its application programming interfaces (APIs) and supports integration with other systems. It typically outlines which APIs are available, any restrictions on their use, and the level of support or uptime that can be expected for these integrations. For example, it may specify that certain APIs are only accessible to premium users or that integration support is limited to specific third-party platforms. The core function of this clause is to set clear expectations regarding the interoperability of the service, helping users understand the extent to which they can connect and automate workflows with other tools.
POPULAR SAMPLE Copied 2 times
Integrations and API Availability. Vendor has and shall have the ability to pull in data feeds using REST APIs, as well as integrate with other REST services from third party applications and integrations such as accounting systems, using a two-way synchronous API. Vendor’s API shall also have the ability to pull in data feeds from third party applications, CRMs, and integrations via JSON, RSS or compatible approach. Vendor shall use this functionality and technology as required to provide the Vendor System and Services as required pursuant to the Agreement. [To be inserted]
1. Vendor shall provide Maintenance and Support Services using Vendor’s specialized Support Representative(s) (also referred to as the “Support Team”) which Representatives shall have appropriate expertise to provide prompt resolution of technical support questions. If Customer reasonably determines that a Vendor Support Representative is not performing satisfactorily, the Parties will attempt to remediate the shortfalls, and if Customer requests, Vendor will designate a new Support Representative acceptable to Customer, which acceptance will not be unreasonably withheld.
1.1 Maintenance and Support Services shall include access to the Vendor Support Team (via [_email/web ].
1.2 A Customer or User request for Maintenance and Support Services shall be referred to as a “Ticket.” Any ticket received Monday through Friday, 6:00 am to 5:00 pm (PST) will be viewed in real-time and assessed for urgency and assigned to the correct Vendor Support Representative(s) for timely resolution. Tickets marked by Customer or User as “urgent” or “priority” will be reviewed and triaged as soon as possible. If the Level 1 Support Team cannot close the Ticket by resolving the associated issues, the Ticket will be escalated to the Support Team lead who will cause the Vendor Project and/or Product/Engineering teams to resolve the issue subject to the Ticket. The Support Team will communicate with the Customer regularly to provide any updates to (or answer questions about) the escalated issue.
1.3 The Parties may jointly determine that an issue requires escalation to the Vendor Development Team. Due to the complexity of issues that are normally worked on by Development Team, resolution time guidelines that the Support Team follows do not necessarily apply upon escalation to the Development Team, although the Development Team shall work to resolve the Ticket expeditiously.
1.4 For each Ticket, the Support Team shall conduct an initial evaluation...