APPLICATION PROGRAMMING INTERFACE (“API”) INTEGRATION Sample Clauses

APPLICATION PROGRAMMING INTERFACE (“API”) INTEGRATION. To provide the Services, Company and Merchant concurrently acknowledge that the electronic systems of both parties may need to electronically integrate and interface, including sending, receiving, and/or transmitting information via the API of Company (“Company API”) and the API of Merchant (“Merchant API”). During the continuance of this Agreement and to the extent it is required for providing Services in accordance with this Agreement, each Party hereby grants to other Party a personal, limited, non- exclusive, non-transferable right and fully paid up license to install and use the API provided by each Party to the other Party. Each Party shall not alter, reproduce, adapt, distribute, display, publish, reverse engineer, translate, disassemble, decompile or otherwise attempt to create any source code that is derived from the API provided by the other Party. The API is provided by each Party on ‘as is’ basis. Except as expressly provided under this Agreement, no right, license or title is granted or shall be deemed to be granted by each Party to the other Party on the API, and all such rights and ownerships are reserved by the provider of the API. Upon termination of this Agreement, or upon any suspension of the Services, each Party shall stop using the API provided by the other Party. Each Party warrants and guarantees that the API provided to the other Party shall comply with all applicable laws and regulations, industry standards and practices and is operated with diligence and care. The API provided by each Party shall not contain any hidden content, malware, spyware, spamware, “Easter Eggs”, trojans, unauthorized key-locks or any other software virus, that is designed and intended to damage, disrupt, shut down, spy upon or otherwise materially and adversely affect the other Party’s computer systems, databases and underlying software, or otherwise harm or destroy any of other Party’s hardware, software, or other property or related information or data. Each Party shall be solely responsible for payment of relevant consideration and indemnifies the other Party against any claims, losses, damages in connection with such third-party rights to the API provided or its use for the purposes of this Agreement.
AutoNDA by SimpleDocs

Related to APPLICATION PROGRAMMING INTERFACE (“API”) INTEGRATION

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Local Switching Interfaces 4.2.13.1 Newcomm shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!