…confirmation. By default this feature is off and will use the base functionality currently provided by DotNetShipping. However, when instantiating a new Package, just set the SignatureRequiredOnDelivery to true. Unit tests have ben wired up for USPS, UPS and FedEx. Currently the only caveat is w/ USPS. If you're doing an ALL lookup (which is the default), the additional service charges will not be returned. The only way to get those charges is to do a specific service lookup (which will then have the additional charges returned). This is a limitation of the USPS API and unfortunately isn't an easy fix. Just as an aside, the average cost of the signature confirmation for most of the carriers is about $4-$5 as of 2/20/2017.
…confirmation. By default this feature is off and will use the base functionality currently provided by DotNetShipping. However, when instantiating a new Package, just set the SignatureRequiredOnDelivery to true. Unit tests have ben wired up for USPS, UPS and FedEx. Currently the only caveat is w/ USPS. If you're doing an ALL lookup (which is the default), the additional service charges will not be returned. The only way to get those charges is to do a specific service lookup (which will then have the additional charges returned). This is a limitation of the USPS API and unfortunately isn't an easy fix. Just as an aside, the average cost of the signature confirmation for most of the carriers is about $4-$5 as of 2/20/2017.