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...
View Source

Related to Integrations and API Availability

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.