UPS® Address Validation API (XML) and ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ Validation API Sample Clauses

UPS® Address Validation API (XML) and ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ Validation API. (XML and Web Services). Any request to the UPS Address Validation API or ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ Validation API shall be solely for the purpose of validating an address in connection with tendering a package intended for delivery via services offered by UPSI. You shall design the Application(s) such that the following language, or such other language provided by UPS from time to time, is conspicuously displayed on the same visible screen as, and in reasonable proximity to, the Information informing the user of an invalid address: “NOTICE: UPS assumes no liability for the information provided by the address validation functionality. The address validation functionality does not support the identification or verification of occupants at an address.” Further, You shall design the Application(s) such that the following language, or such other language provided by UPS from time to time, is conspicuously displayed on the same visible screen as, and in reasonable proximity to, Information returned from the UPS Address Validation API or Street Level Address Validation API informing the user either (at Your option): (a) with respect to a P.O. Box address or (b) with respect to any address: “NOTICE: The address validation functionality will validate P.O. Box addresses. However, UPS does not deliver to P.O. Boxes. Attempts by customer to ship to a P.O. Box via UPS may result in additional charges.”
View Source

Related to UPS® Address Validation API (XML) and ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇ Validation API

  • Inspection and Testing Each Constructing Entity shall cause inspection and testing of the Interconnection Facilities that it constructs in accordance with the provisions of this section. The Construction Parties acknowledge and agree that inspection and testing of facilities may be undertaken as facilities are completed and need not await completion of all of the facilities that a Constructing Entity is building.

  • Inspection and Rejection of Nonconforming Goods The Buyer has the right to inspect the Goods on or after the Delivery Date. Buyer, at its sole option, may inspect all or a sample of the Goods, and may reject all or any portion of the Goods if it determines the Goods are nonconforming or defective. If Buyer rejects any portion of the Goods, Buyer has the right, effective upon written notice to Seller, to: (a) rescind the Order in its entirety; (b) accept the Goods at a reasonably reduced price; or (c) reject the Goods and require replacement of the rejected Goods. If Buyer requires replacement of the Goods, Seller shall, at its expense, promptly replace the nonconforming Goods and pay for all related expenses, including, but not limited to, transportation charges for the return of the defective goods and the delivery of replacement Goods. If Seller fails to timely deliver replacement Goods, Buyer may replace them with goods from a third party and charge Seller the cost thereof and terminate this Order for cause pursuant to Section 19. Any inspection or other action by Buyer under this Section shall not reduce or otherwise affect Seller's obligations under the Order, and Buyer shall have the right to conduct further inspections after Seller has carried out its remedial actions.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Inspection and Tests 3.8.1 The Procuring entity or its representative shall have the right to inspect and/or to test the goods to confirm their conformity to the Contract specifications. The Procuring entity shall notify the tenderer in writing in a timely manner, of the identity of any representatives retained for these purposes. 3.8.2 The inspections and tests may be conducted in the premises of the tenderer or its subcontractor(s), at point of delivery, and/or at the Goods’ final destination If conducted on the premises of the tenderer or its subcontractor(s), all reasonable facilities and assistance, including access to drawings and production data, shall be furnished to the inspectors at no charge to the Procuring entity. 3.8.3 Should any inspected or tested goods fail to conform to the Specifications, the Procuring entity may reject the equipment, and the tenderer shall either replace the rejected equipment or make alterations necessary to make specification requirements free of costs to the Procuring entity. 3.8.4 The Procuring entity’s right to inspect, test and where necessary, reject the goods after the Goods’ arrival shall in no way be limited or waived by reason of the equipment having previously been inspected, tested and passed by the Procuring entity or its representative prior to the equipment delivery. 3.8.5 Nothing in paragraph 3.8 shall in any way release the tenderer from any warranty or other obligations under this Contract.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.