Integrations and API Availability Sample Clauses

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. SCHEDULE 2.10 HOSTING SERVICES [To be inserted] SCHEDULE 2.11 MAINTENANCE AND SUPPORT SERVICES
AutoNDA by SimpleDocs

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 System Availability percentage is calculated as follows:  Total MinutesintheMonth −Downtime   System Availability%age =  Total MinutesintheMonth *100    System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.

  • 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.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • Availability of Services CBT agrees not to discontinue or refuse to provide any service provided or required hereunder other than in accordance with the terms of this Agreement, or unless required by the Commission.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

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