Menu
PLEASE NOTE: As of January 25th, our customers have reported to us that UPS will be sunsetting their Freight API on April 30th, just over a month before the rest of their APIs are affected. Please get in touch with us soon to discuss how these changes will impact your business.
APIs are evolving and so are we. With UPS and FedEx completely updating their APIs in the coming months, we’re here to help you understand these changes, the impacts, and how our solutions can support a seamless transition.
The world of shipping and logistics doesn’t just change course; sometimes it undergoes transformative shifts. Sweeping updates are coming to UPS and FedEx APIs – you need to be prepared.
UPS API Paradigm Shift:
This isn’t a simple enhancement or update. UPS is replacing its entire existing API infrastructure. The previous access key-based authorization is being deprecated in favor of the more secure OAuth 2.0 security model, requiring a bearer token for every API request. From June 5, 2023, no new access keys will be distributed, and post-June 3, 2024, any transaction with UPS will mandate this new OAuth security model.
Moreover, in this extensive overhaul, UPS is transitioning to a true RESTful pattern, offering more flexibility. Any prior integrations, be it XML, SOAP, or legacy JSON payloads, will necessitate a complete transformation to align with UPS’s RESTful APIs from their new API Catalog.
To underline the extent of this change: If you’ve ever used an Access Key for authorization or have been instructed by a software provider to do so, your current integration is immediately impacted. This mandates a comprehensive review and update of your system integrations. If an external vendor manages your integration, alert them instantly.
FedEx API Transition:
FedEx isn’t just updating its API; it’s championing a digital transformation. While their new API has been available for some time, the transition window is rapidly closing.
FedEx announced on August 18, 2022 that the previous FedEx Web Services WSDLs are heading for retirement. Developers have until May 15, 2024 to adopt the improved FedEx API, at which point previous SOAP APIs will become completely inaccessible.
Developers are increasingly leaning towards REST APIs, thanks to their flexibility and efficiency. Acknowledging this trend, FedEx has crafted modernized REST APIs aiming to refine integration capabilities. The benefits are manifold: ease of integration, faster performance, enhanced scalability, and superior versioning management, to name a few. In addition, their new developer portal aims to redefine the API integration experience with a modernized user interface.
The Undercurrent:
This is more than mere news; it’s a clarion call for action. Platforms like Drupal, Magento, NopCommerce, and Acumatica for UPS, and EPIUsers, Acumatica, and WooCommerce for FedEx, are all abuzz discussing these monumental changes. If you’d like to learn more from the shipping companies themselves, both UPS and FedEx provide detailed migration advice.
The clock is ticking, and the deadlines – June 2024 for UPS and May 2024 for FedEx – are closer than they appear.
These API changes mean that you may need to update or even rebuild your current FedEx or UPS integration, depending on whether you’re using our UPS Toolkit for i (UPSTI), RPG API Express (RXS), or a custom solution.
We understand that changes like these can be challenging, but have no fear – we’re here to help.
The landscape of shipping APIs is changing, but with Kato Integrations, you have a trusted partner to navigate the journey. Reach out to us today to start your smooth transition.