Types of Advanced Integrated Visibility Webhooks
The Advanced Integrated Visibility webhook allows FedEx to push near real-time secured tracking event data to a destination URL for shipments associated with specific FedEx account number(s).
You can create an Advanced Integrated Visibility webhook project on the FedEx Developer Portal and then associate it with one or more FedEx account numbers or FedEx tracking numbers based on your selected subscription type.
Navigate to:
ADVANCED INTEGRATED VISIBILITY ACCOUNT NUMBER SUBSCRIPTION or ADVANCED INTEGRATED VISIBILITY TRACKING NUMBER SUBSCRIPTION , to view the steps to create the respective Advanced Integrated Visibility webhook.
FedEx Advanced Integrated Visibility Overview
FedEx customers can subscribe to Account number or Tracking number to receive near real time in-transit shipment events, from label creation to Proof of delivery of packages, including Picture Proof of Delivery.
Subscription Types
FedEx customers can subscribe to Advanced Integrated Visibility by the following options:
- By Account Number- Subscribe to FedEx Account Number to receive updates for shipments matched to the account.
- By Tracking Number- Subscribe to FedEx Tracking Number to receive updates for shipments matched to the specified tracking numbers through API endpoints.
Note: Subscriptions currently require U.S. based FedEx 9-digit account for billing, and customers are charged a monthly fee based on the count of Tracking Numbers. To know more about the pricing of the Advanced Integrated Visibility refer to the Advanced Integrated Visibility Overview Pricing Guide.
If subscribed by Account number, Subscriptions currently require FedEx 9 digit US based shipping accounts.
Below table gives you the information about the features of account number subscription and Advanced integrated visibility tracking number subscription
| Features | Account Number Subscription | Tracking Number Subscription |
|---|---|---|
| Response | Secured data = Personally identifiable information (PII) data Shipper and Recipient data SPOD CDOs (Convenient Delivery Option)/response | Anonymous data(Includes Shipment, In-Transit updates excluding PII - Personally identifiable information/response |
| Association | Association by an account number = Associating all linked tracking numbers at once | Association of tracking numbers |
| Ownership | Account numbers need to be owned by user themselves | Tracking numbers need not be owned by the user |
| Filtering | Has the ability to filter events by inbound, outbound and third-party shipments |
Cannot filter events |
| Integration | Association of account numbers is through UI | Association of tracking numbers is through API endpoint |
| Limitation | Can add upto 1000 account numbers | Can add upto 1000 tracking number per request |
| Suitable Use Case | 1st party customers- If customer owns the account numbers | 3rd party customers- If customer has tracking numbers belonging to 1st party customers |
FedEx Integrated Visibility – Feature Comparison by Subscription Type
| Feature / Data Element | Tracking Number Subscription | Account Number Subscription | Notes |
|---|---|---|---|
| SPOD (Signature Proof of Delivery) | Not Available | Available (config required) | Signature image in TIFF format, delivered in payload |
| PPOD (Picture Proof of Delivery) | Available (config required) | Available (config required) | JPEG image of delivery location, base64 encoded |
| PPODA (Picture Proof of Delivery Attempt) | Available (config required) | Available (config required) | For delivery attempts, JPEG image provided |
| GPS Coordinates (gpsPodCoordinates) | Not Available | Available | Masked in tracking-based subscriptions |
| Contact Info (Name, Phone, Company) | Masked | Available | Across shipper, recipient, origin, destination, broker, etc. |
| Street Address & Postal Code | Masked | Available | streetLines and postalCode are masked in tracking-based payloads |
| Account Numbers | Masked | Available | Includes billTo, shipper, and recipient account values |
| Package Financials (e.g., declaredValue, codAmount) | Masked | Available | Customs, COD, and declared values are masked |
| Inquiry & Return Details (Inquiry codes, Return reasons) | Masked | Available | Full details only shown for account-based subscribers |
| Commodity & Contents Data | Masked | Available | Includes part codes, descriptions, quantitie |
| Employee ID (e.g., event personnel) | Masked | Not Available | Masked in both cases for privacy reasons |
| Event Notifications & EDD/EDTW | Available | Available | Estimated delivery date/time features supported on both |
| Multi-Parcel Shipment (MPS) | Available | Available | With additional tracking info |
| Estimated Delivery Confidence & Risk Scores | Available | Available | Part of Premium Tier only |
Masked Data Fields for Advanced Integrated Visibility Tracking Number Subscription
Summary
When customers subscribe to shipment tracking updates using the Advanced Integrated Visibility Tracking Number Subscription instead of the Advanced Integrated Visibility Account Number Subscription, specific data fields are masked to maintain customer privacy and comply with data security policies.
This masking ensures that sensitive information—such as personal contact details, addresses, and financial values—is only accessible to authorized parties. Customers using the Advanced Integrated Visibility Tracking Number Subscription will see ‘XXXXX’ for the masked fields listed below, even though this data may be available through the Advanced Integrated Visibility Tracking Number Subscription.
The implications of this masking include:
- Limited visibility into origin/destination details and involved parties.
- Absence of personal identifiers (e.g., names, phone numbers) and financial or customs-related data.
- Designed protection of proprietary or sensitive shipment information for security and regulatory compliance.
Customers requiring access to these masked fields for operational or business use cases are advised to subscribe using their Account Number.
Data points that are MASKED in Advanced Integrated Visibility Tracking Number Subscription:
Scan Events
- scanEvent/location/locationContactAndAddress/address/streetLines
- scanEvent/location/locationContactAndAddress/contact/phoneNumber
- scanEvent/location/locationContactAndAddress/contact/companyName
- scanEvent/location/locationContactAndAddress/contact/personName
- scanEvent/previousEvents/[Array]/location/locationContactAndAddress/address/streetLines
- scanEvent/previousEvents/[Array]/location/locationContactAndAddress/contact/phoneNumber
- scanEvent/previousEvents/[Array]/location/locationContactAndAddress/contact/companyName
- scanEvent/previousEvents/[Array]/location/locationContactAndAddress/contact/personName
Shipper Information
- trackResult/shipperInfo/contactAndAddress/address/postalCode
- trackResult/shipperInfo/contactAndAddress/address/streetLines
- trackResult/shipperInfo/contactAndAddress/contact/phoneNumber
- trackResult/shipperInfo/contactAndAddress/contact/companyName
- trackResult/shipperInfo/contactAndAddress/contact/personName
- trackResult/shipperInfo/account/value
Recipient Information
- trackResult/recipientInfo/contactAndAddress/address/postalCode
- trackResult/recipientInfo/contactAndAddress/address/streetLines
- trackResult/recipientInfo/account/value
- trackResult/recipientInfo/contactAndAddress/contact/phoneNumber
- trackResult/recipientInfo/contactAndAddress/contact/companyName
- trackResultecipientInfo/contactAndAddress/contact/personName
Origin & Destination Location
- trackResult/originLocation/locationDetail/locationContactAndAddress/contact/personName
- trackResult/originLocation/locationDetail/locationContactAndAddress/contact/phoneNumber
- trackResult/originLocation/locationDetail/locationContactAndAddress/contact/companyName
- trackResult/originLocation/locationDetail/locationContactAndAddress/address/streetLines
- trackResult/originLocation/locationDetail/locationContactAndAddress/address/postalCode
- trackResult/destinationLocation/locationDetail/locationContactAndAddress/contact/personName
- trackResult/destinationLocation/locationDetail/locationContactAndAddress/contact/phoneNumber
- trackResult/destinationLocation/locationDetail/locationContactAndAddress/contact/companyName
- trackResult/destinationLocation/locationDetail/locationContactAndAddress/address/streetLines
- trackResult/destinationLocation/locationDetail/locationContactAndAddress/address/postalCode
Delivery and Address Change Details
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/address/streetLines
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/address/postalCode
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/address/gpsPodCoordinates
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/contact/personName
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/contact/phoneNumber
- trackResult/actualDeliveryAddress/locationDetail/locationContactAndAddress/contact/companyName
- trackResult/addressChangeRequested/locationDetail/locationContactAndAddress/address/streetLines
- trackResult/addressChangeRequested/locationDetail/locationContactAndAddress/address/postalCode
- trackResult/addressChangeRequested/locationDetail/locationContactAndAddress/contact/personName
- trackResult/addressChangeRequested/locationDetail/locationContactAndAddress/contact/phoneNumber
- trackResult/addressChangeRequested/locationDetail/locationContactAndAddress/contact/companyName
Broker Information
- trackResult/broker/locationDetail/locationContactAndAddress/contact/phoneNumber
- trackResult/broker/locationDetail/locationContactAndAddress/contact/companyName
- trackResult/broker/locationDetail/locationContactAndAddress/contact/personName
- trackResult/broker/locationDetail/locationContactAndAddress/address/streetLines
- trackResult/broker/locationDetail/locationContactAndAddress/address/postalCode
Package and Financial Details
- trackResult/packageDetail/customsValue/value
- trackResult/packageDetail/declaredValue/value
- trackResult/packageDetail/originalTransportationCharge/value
- trackResult/codDetail/codAmount/value
Inquiry & Commodity Information
- trackResult/inquiries/[Array]/categoryCode
- trackResult/inquiries/[Array]/code
- trackResult/inquiries/[Array]/createTime
- trackResult/inquiries/[Array]/statusCode
- trackResult/commodityInfo/[Array]/description
- trackResult/commodityInfo/[Array]/code
Package Contents & Return Reason
- trackResult/contents/[Array]/partNumber
- trackResult/contents/[Array]/partCode
- trackResult/contents/[Array]/description
- trackResult/contents/[Array]/quantity
- trackResult/returnReason/[Array]/code
- trackResult/returnReason/[Array]/description
Billing Information
- trackResult/billToParties/[Array]/billToParty/accountNumber
Customer Benefits:
- Improve recipient confidence with proactive notifications for in-transit changes to Estimated Delivery Date and day of delivery Time Window.
- Reduce customer service costs for WISMO (Where Is My Order) calls as well as delivery disputes by providing FedEx Picture Proof of Delivery.
- Enhance customer experience by providing near real time notifications on shipment status.
- Gain operational efficiencies by receiving real time push update on shipments, instead of polling continuously to check for track updates on every shipment.
Features and Tracking Events
Tracking Events
This feature allows to track the status of shipments proactively notify customers on different updates in the shipment lifecycle. It provides the customers with options to choose the exact stage of the shipment process/events they wish to receive a notification/alert for. The available shipping events are:
- Ship: This option provides notification when the selected shipment event occurs. Example: Label Created, Pickup, etc.
- In transit: This option provides notification for the shipment transit events. Example: In transit, item held at delivery office, etc.
- Delivery: This option provides notification for the shipment delivery events. Example: out for delivery, delivered, etc.
- Exceptions: This option provides notification for the delivery exceptions. Example: clearance delay, etc.
- Convenient delivery options: Select this option to receive notification for some personalized tracking events. Example: hold at location request accepted.
For more information on the available shipment event options, refer to the Status Codes and Statuses for Advanced Integrated Visibility Tracking Events table.
Proof of Delivery
This feature is used to acknowledge an order has successfully arrived at its intended destination. This includes:
- Picture proof of delivery (PPOD): PPOD allows customers to receive a picture of the exact location of their package once it is delivered to their doorstep.
Advanced Integrated Visibility delivers the PPOD images in the JSON payload in a base64 format. The images can then be converted to a JPEG format.
Note:
- PPOD is available in the U.S., Canada, Puerto Rico, Hong Kong, New Zealand, United Kingdom, and Ireland.
- PPOD is only available for FedEx Ground, FedEx Express and residential packages/address(es).
- PPOD is available for eligible deliveries when SPOD is not required. PPOD and SPOD are not available together.
- PPOD is available for on-signature required (NSR) deliveries that are not given directly to a customer (e.g. handed directly to a customer during delivery).
- PPOD supports image size from 14000 to 33000 bytes (Applicable for 320 x 240 resolution image).
- Picture proof of delivery attempt (PPODA): PPODA allows customers to receive a picture of the exact location of where the package is to be delivered, in the event that delivery cannot be completed. Advanced Integrated Visibility delivers the PPODA images in the JSON payload in a base64 format. The images can then be converted to a JPEG format.
- PPODA is available in the U.S. and Puerto Rico.
- PPODA is only available for FedEx Ground, FedEx Express and residential and commercial packages/address(es).
- PPODA Image can be:
- PPODA image photo of Doortag on Door.
- Photo of Obstruction to Delivery Point (i.e., locked gate).
- PPOD Image of Packages Delivered at the stop.
- PPODA supports image size from 14000 to 33000 bytes (Applicable for 320 x 240 resolution)
- Signature proof of delivery (SPOD): SPOD allows customers to receive an image of the recipient’s signature as well as their name delivery date, time and location. The SPOD information will be presented as a byte array instead of an image. The byte array is a base64 encoded string, which should be decoded to get the final signature image in PNG format
- SPOD is not available for Advanced Integrated Visibility Tracking Number Subscription.
- The SPOD image size will be from 4000 to 6000 bytes (Applicable for 400x95 resolution image).
- The SPOD image size will be from 5000 to 8000 bytes (Applicable for 230x150 resolution image).
- GPS proof of delivery (GPSPOD):
- GPS POD allows customers to receive the geographical coordinates of the delivery location.
Note: GPSPOD is available by default for advanced integrated visibility account number subscription.
- GPS POD allows customers to receive the geographical coordinates of the delivery location.
Estimated Delivery Date and Delivery Time Window Events
This feature helps recipients of the shipments plan their schedules by providing a date and/or time range for shipment deliveries. This includes:
- Estimated delivery date (EDD): This option provides an estimated date of delivery of the shipment to the recipient. Example: Nov, 20, 20XX.
- Estimated delivery time window (EDTW): This option provides the recipient with an estimated time window for the shipment delivery on the day of actual delivery. Example: 2pm to 6pm.
Event Based Filtering
This feature allows customers to organize their webhook projects based on the billing methods for the shipments. The options are:
- Inbound: select this option for shipments that will be delivered to you and will be paid for, by you as the recipient.
- Outbound: select this option for shipments that will be shipped by you and will be paid for, by you as the sender.
- Third-party: select this option for inbound and outbound shipments that are billed to you as a third-party payer.
Note: Your FedEx account number will be used to bill or pay for the shipments. For third-party payer, you may not be the shipper or recipient, but the charges will be billed to your FedEx account number.
Retry Policy
This feature prevents FedEx from sending tracking event data in the event of a client-side issue. FedEx will hold the data and attempt to resend it within a span of 3 retries within 5 minutes intervals.
If FedEx does not receive a successful response in the defined time span, then FedEx will stop redelivery of that specific event. However, customer can request for missed events over a period of last 7 days through a manual "RETRY" button on the Advanced Integrated Visibility webhook project Details page.
For more information on retry policies, refer to the Retry mechanism section.
