August 12, 2025
FedEx Advanced Integrated Visibility Enhancements in July 2025 and Upcoming releases
As part of our ongoing efforts to improve Webhook product, customer visibility, and integration experiences, we’re introducing and have deployed several key updates listed below.
Release Date: July 31 2025
- Ability to add same shipping account numbers in multiple Webhook subscriptions in an organization.
- Redesigned webhook documentation pages to improve readability.
- Defect fix - Sandbox URLs removed from Account Number subscription API and Track Number Subscription APIs. Production URLs are displayed as default.
- Defect fix - Fixed Webhook dashboard UI issues to enable users to view and search across large volume of shipping account numbers.
Upcoming Enhancements – September 2025
- Standardization of event descriptions (removal of full stops).
- Removal of deprecated fields in the tracking schema.
- Adding address details, facility type in Hold at location, Pick Up nodes.
Additional details:
Please review the release details below to ensure upcoming changes do not negatively affect your webhook integration.
July 31, 2025, Release - Detailed Notes
1. Shipping Account Duplication across webhook subscriptions
Customers add same shipping account number across multiple subscription IDs during webhook creation or updates within the same organization, no country restrictions apply.
Example Scenario:
- Shipping Account Number: ABC123456
- Subscription IDs: SubscriptionID-001, SubscriptionID-002, SubscriptionID-003
You can now add ABC123456 to all three subscriptions during webhook creation or updates, enabling consistent tracking and event handling across your organization’s systems.
Updated webhook documentation
The webhook documentation page now features clearer, more detailed descriptions, with improved formatting and visual aids to support developers.
Defect Fixes
- As part of this release, we are sharing only the Production Server URLs in the API Endpoints documentation for both the Account Number Subscription API and the Tracking Number Subscription API. This is intended to ensure clarity, reduce confusion, and support production-ready implementations.
- We have resolved an issue where users encountered an error while attempting to create a webhook on the FedEx Developer Portal (FDP) using bulk shipping accounts. This error was caused by the inability to load or display the full list of accounts during the webhook setup process. Users can now successfully view and select all accounts when configuring webhooks with multiple shipping accounts.
Upcoming Release Details - September 2025
Deails of upcoming releases are provided below for your review. Upon completion of the necessary development work, we will promptly share a detailed release schedule.
1. Standardization of Event Descriptions in Webhook Data
To ensure consistency across systems and integrations, we are removing full stops (periods) from event descriptions. This change applies to all event types and helps maintain uniform formatting across platforms.
What this means for your webhook integration?
If your systems rely on exact event description formats (e.g., for parsing or matching), this may be a breaking change.
A full list of affected event descriptions is provided below.
| Current Event Description (Before) | New Event Description (After) |
|---|---|
| Manifest Data at Airport. | Manifest Data at Airport |
| Cleared Customs at Customs Broker. | Cleared Customs at Customs Broker |
| Arrived At Customs Broker. | Arrived At Customs Broker |
| Clearance Delay at Customs Broker. | Clearance Delay at Customs Broker |
| Arrived At Destination FedEx Facility. | Arrived At Destination FedEx Facility |
| At Destination FedEx Facility. | At Destination FedEx Facility |
| Arriving On-time at Destination FedEx Facility. | Arriving On-time at Destination FedEx Facility |
| Arriving Early at Destination FedEx Facility. | Arriving Early at Destination FedEx Facility |
| Ready for Pickup at Destination FedEx Facility. | Ready for Pickup at Destination FedEx Facility |
| Delivery Exception at Destination FedEx Facility. | Delivery Exception at Destination FedEx Facility |
| Delay at Destination FedEx Facility. | Delay at Destination FedEx Facility |
| Hold at Destination FedEx Facility. | Hold at Destination FedEx Facility |
| Arrived At Delivery Location. | Arrived At Delivery Location |
| Delivery Exception at Delivery Location. | Delivery Exception at Delivery Location |
| Arriving On-time at Delivery Location. | Arriving On-time at Delivery Location |
| Arriving Early at Delivery Location. | Arriving Early at Delivery Location |
| Delivery Delay at Delivery Location. | Delivery Delay at Delivery Location |
| Delivery Option Request Cancelled at Enroute. | Delivery Option Request Cancelled at Enroute |
| Arriving Early at Enroute. | Arriving Early at Enroute |
| Arriving On-time at Enroute. | Arriving On-time at Enroute |
| Pickup Delay at Enroute. | Pickup Delay at Enroute |
| Cleared Customs at Enroute. | Cleared Customs at Enroute |
| Delivery Delay at Enroute. | Delivery Delay at Enroute |
| Cleared Customs at FedEx Facility. | Cleared Customs at FedEx Facility |
| Clearance Delay at FedEx Facility. | Clearance Delay at FedEx Facility |
| At FedEx Facility. | At FedEx Facility |
| Departed from FedEx Facility. | Departed from FedEx Facility |
| Arrived At FedEx Facility. | Arrived At FedEx Facility |
| Clearance in Progress at FedEx Facility. | Clearance in Progress at FedEx Facility |
| Arriving On-time at FedEx Facility. | Arriving On-time at FedEx Facility |
| Arriving Early at FedEx Facility. | Arriving Early at FedEx Facility |
| Arrived At Origin FedEx Facility. | Arrived At Origin FedEx Facility |
| Delay at FedEx Facility. | Delay at FedEx Facility |
| Departed from Origin FedEx Facility. | Departed from Origin FedEx Facility |
| In FedEx Possession at FedEx Facility. | In FedEx Possession at FedEx Facility |
| Transfer at FedEx Facility. | Transfer at FedEx Facility |
| On Demand Care at FedEx Facility. | On Demand Care at FedEx Facility |
| Arriving On-time at Origin FedEx Facility. | Arriving On-time at Origin FedEx Facility |
| Arriving Early at Origin FedEx Facility. | Arriving Early at Origin FedEx Facility |
| Clearance Delay at Origin FedEx Facility. | Clearance Delay at Origin FedEx Facility |
| Location changed at Origin FedEx Facility. | Location changed at Origin FedEx Facility |
| Cleared Customs at Origin FedEx Facility. | Cleared Customs at Origin FedEx Facility |
| Transfer at Origin FedEx Facility. | Transfer at Origin FedEx Facility |
| Arriving On-time at Pickup Location. | Arriving On-time at Pickup Location |
| Arriving Early at Pickup Location. | Arriving Early at Pickup Location |
| In FedEx Possession at Pickup Location. | In FedEx Possession at Pickup Location |
| Arriving Early at Vehicle. | Arriving Early at Vehicle |
| Arriving On-time at Vehicle. | Arriving On-time at Vehicle |
| Departed from Destination. | Departed from Destination |
| Arrived At Destination. | Arrived At Destination |
| Arriving Early at Destination. | Arriving Early at Destination |
| Arriving On-time at Destination. | Arriving On-time at Destination |
| Arrived At Pickup Location. | Arrived At Pickup Location |
| Pickup Delay at Pickup Location. | Pickup Delay at Pickup Location |
2. Schema Cleanup and Field Removals
To reduce redundancy and simplify payloads, the following fields will be removed from the tracking response schema:
- scanEvent/eventAdditionalInfo/employeeId
- scanEvent/previousEvents/[Array]/eventAdditionalInfo/employeeId
- trackResult/documents/[Array]/systemId
- trackResult/documents/[Array]/lineNbr
- trackResult/documents/[Array]/recordId
- trackResult/documents/[Array]/folderId
These fields are no longer required and will be deprecated in upcoming releases.
3. Enhancement to Hold Location, Ready for Pick up events
We are adding location details. Previously, hold events displayed:
Hold at <Facility>
This will now be replaced with:
Hold at <Address> (<Facility Type>)
This change gives customers clearer visibility into the exact location where their package is being held for pickup, improving the overall delivery experience.
"Ready for Pickup" event by unmasking and adding the address line directly into the event description. This enhancement allows customers to immediately see where their package is available for pickup without needing to reference additional fields.
Example:
Before:
PickUp at FedEx Office
After:
Ready for recipient pickup
(Package available for pickup at FedEx Office – 610.9TH ST), DURHAM, NC
This helps customers know exactly where to go to retrieve their packages, especially helpful when multiple FedEx locations exist nearby.
