Ups Api Laravel Package

What's Changed

• reduce copy/past ref. AccountNumber by @xerc in https://github.com/gabrielbull/php-ups-api/pull/352
• Allow psr/log >= 3.0. by @ptondereau in https://github.com/gabrielbull/php-ups-api/pull/355

New Contributors

• @xerc made their first contribution in https://github.com/gabrielbull/php-ups-api/pull/352

Full Changelog: https://github.com/gabrielbull/php-ups-api/compare/2.0.4...2.1.0

What's Changed

• Add VendorInfo to support the new IOSS , HMRC and VOEC number created… by @jay1963 in https://github.com/gabrielbull/php-ups-api/pull/334

New Contributors

• @jay1963 made their first contribution in https://github.com/gabrielbull/php-ups-api/pull/334

Full Changelog: https://github.com/gabrielbull/php-ups-api/compare/2.0.3...2.0.4

What's Changed

• Carbon neutral option added the Missing Create Element and Append it to Current Node by @Shehryar2 in https://github.com/gabrielbull/php-ups-api/pull/338

Full Changelog: https://github.com/gabrielbull/php-ups-api/compare/2.0.2...2.0.3

Add: #336

• Fix mistakes #325 @DeryabinSergey

• chore(php): Remove PHP 7.1 and 7.2 support. #320
• Fix createRecoveryLabelRequest #318

• Added TaxInformationIndicator support (#307) (@hubertsmusz)

• Removed PHP 5.5, 5.6 and 7.0 support
• Add Guzzle 7 support (thanks @neoteknic #289)
• Add support of PHP 8.0
• Update PHPUnit to version 7 or 9.3

Implement Ratetimeintransit and Shoptimeintransit requests

• Allow reference number 2 on package
• Add support for DeliveryConfirmation
• Allow multiple tracking data (array) in single request

• Extend ShipmentServiceOptions in Shipping API
• Fix for Begin and End date in Tracking API
• Support for HazMat containers in Shipping API

• The Tracking API now supports multiple results on one reference number. It can be activated using a feature flag.
• A second Address Validation class has been added. The existing one only works for US/PR customers of UPS, while this one supports way more countries (e.g. European countries). The options and results are less extensive.

• Add Shipping API Support for AdditionalDocumentIndicator in the InternationalForms node
• Add Shipping API Support for EEIFilingOption in the InternationalForms node
• Add TimeInTransit API Response Service Code Constants for US/EU Shipments to Entity/Service.php
• Add Tracking API Response StatusType Constants

• Adds support for a second reference number on Shipments

• [!] Default ShipFrom on Shipment class not set anymore in constructor (ShipFrom is optional)
• Adds support for cash on delivery for shipments

Items marked with [!] may incur backwards incompatibility.

The XML response was proper stripped of namespaces (to work easier with), but the XML string was still having namespaces. In the case users want to cache the string, they need to refactor it afterwards again. This change prohibits that.

Landed Cost endpoint can be used to estimate import duties the receiver has to pay when sending using the prepaid shipping method. Can also be used to calculate the costs to charge to the client when using the option to pay for all duties (free domicile).

Note that the Tradeability API requires the usage of SOAP, so you need to have the php-soap extension installed. Also note that the Tradeability API consist of 4 endpoints, of which Landed Cost is the first one.

Original Tracking class had only support for tracking based on shipment number. This change adds the functionality to also track it based on Reference Number. A reference number can be, e.g., the invoice number supplied while creating the shipment.

0.6.0 (released 25-09-2015)

• Extra check on response in QuantumView, when no response it gave an error
• Added ShipmentRequestLabelSpecification class for easier options setting
• Added ShipmentRequestReceiptSpecification class for easier options setting
• [!] Shipment class dropped some public properties in favor of private properties and setter/getter methods.
• [!] confirm and accept methods of Shipping class now receive Shipment, ShipmentRequestLabelSpecification and ShipmentRequestReceiptSpecification

Items marked with [!] may and will incur backwards incompatibility.