ÃÛ¶¹ÊÓƵ

DocumentationCommerceCommerce KB

FedEx shipping method integration migration from SOAP to RESTful API

Last update: Wed Jan 29 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer
WARNING
Use the ACSD-61622 patch from Quality Patches Tool (QPT) 1.1.57 release instead of the previously provided patch. The new patch is compatible with ÃÛ¶¹ÊÓƵ Commerce versions (all deployment methods) 2.4.6-p1 - 2.4.6-p8. It might become applicable to other versions with new Quality Patches Tool releases.
For more information, refer to the ACSD-61622 patch article in our ÃÛ¶¹ÊÓƵ Commerce Tools guide.
WARNING
Before installing the new patch, you need to uninstall the previous patch provided in this article. For instructions on uninstalling patches, refer to Revert a Custom Patch in our user guide.

This article provides a patch to resolve issues with the FedEx shipping method integration migration from SOAP to RESTful API for ÃÛ¶¹ÊÓƵ Commerce 2.4.4-p4 - 2.4.6-pX.

FedEx Web Services tracking, Address Validation, and Validate Postal Codes Web Services Definition Languages (WSDLS) was retired on May 15, 2024. The SOAP based FedEx Web Services is in development containment and has been replaced with FedEx RESTFUL APIs. To learn more, refer to .

This change impacts our current FedEx shipping method integration implementation in ÃÛ¶¹ÊÓƵ Commerce and requires we fix our current implementation and migrate from deprecated SOAP APIs to the latest FedEx RESTFUL APIs.

Beginning on May 15, 2024, ÃÛ¶¹ÊÓƵ Commerce customers will not be able to use our current FedEx shipping method integration, so ÃÛ¶¹ÊÓƵ is releasing this hotfix that allows ÃÛ¶¹ÊÓƵ Commerce 2.4.4+ customers to use the latest FedEx RESTFUL APIs instead of the deprecated SOAP ones.

Affected products and versions

ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure and on-premises, and Magento Open Source:

  • 2.4.4-p4
  • 2.4.5
  • 2.4.5-pX
  • 2.4.6
  • 2.4.6-pX

Cause

The FedEx deprecated their SOAP based APIs and replaced them with the RESTful ones instead. Refer to .

Solution

Use the following attached patches, depending on your ÃÛ¶¹ÊÓƵ Commerce/Magento Open Source version:

To resolve the issue in the 2.4.4+, 2.4.5+, and 2.4.6+ versions, you must apply the corresponding patch to your version of ÃÛ¶¹ÊÓƵ Commerce/Magento Open Source below.

Patch

Use the following attached patches, depending on your ÃÛ¶¹ÊÓƵ Commerce/Magento Open Source version:

For versions 2.4.4-p4:

For versions 2.4.5, 2.4.5-pX:

For versions 2.4.6, 2.4.6-pX:

How to apply the patch

Unzip the file and see How to apply a composer patch provided by ÃÛ¶¹ÊÓƵ in our support knowledge base for instructions.

How to tell whether the patches have been applied

Considering that it is not possible to easily check if the issue was patched, you might want to check whether the patch has been successfully applied. This uses (Example: AC-9363) as the patch to check.

You can do this by taking the following steps:

  1. Install the Quality Patches Tool.

  2. Run the command:

    code language-bash 
    vendor/bin/magento-patches -n status |grep "9363|Status"

  3. You should see output similar to this, where AC-9363 returns the  Applied  s³Ù²¹³Ù³Ü²õ:

    code language-bash 
    ║ Id            │ Title                                                        │ Category        │ Origin                 │ Status      │ Details                                          ║ ║ N/A           │ ../m2-hotfixes/AC-9363_USPS_Ground_Advantage_shipping_method_COMPOSER_patch.patch      │ Other           │ Local                  │ Applied     │ Patch type: Custom
recommendation-more-help
8bd06ef0-b3d5-4137-b74e-d7b00485808a