Bugfix - switched node names in XAV

0.7.4

Update CHANGELOG.md

Mail Innovation in Tracking & Validation result object

0.7.3

Adjusted changelog for 0.7.2

Fix: Use SoapRequest instead of Request in Tradeability

Merge pull request #75 from styks1987/master

Update Tradeability to use SoapRequest instead of Request

Adds support for a second reference number on Shipments

• Adds support for a second reference number on Shipments

ShipFrom optional in Shipment & Cash on delivery for 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.

Minor improvement in parsing XML of Tradeabilty

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.

Added Landed Cost (Tradeabilty) request (using SOAP)

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.

Added Tracking by ReferenceNumber functionality

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.

Refactoring of the Shipping class (potential bc)

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.

Hotfix handling single ServiceSummary response in TimeInTransit

0.5.2

Adjusted changelog to incorporate hotfix