Ship API
Overview

This API allows you to process and submit shipping requests to produce a shipping label or return label and cancel shipments before they are tendered.

Supported Services: 

Package shipments (FedEx Express®, FedEx Ground  and FedEx Ground® Economy).
Refer to LTL Freight API to manage Less-Than-Truckload Freight shipments (FedEx Freight®).

VERSION
V0
LAST UPDATED
07/27/2020

This API allows you to process and submit shipping requests to produce a shipping label or return label and cancel shipments before they are tendered.

Supported Services: 

Package shipments (FedEx Express®, FedEx Ground  and FedEx Ground® Economy).
Refer to LTL Freight API to manage Less-Than-Truckload Freight shipments (FedEx Freight®).


Key Features

Paper icon

Create labels

Produce shipping labels for the supported services. View the FedEx Service Guide  for additional information.

Desktop icon

Manage shipments

Manage your shipping program by creating new shipments or deleting shipments that have not already been tendered to FedEx.

Information icon

Notifications

Request that FedEx notify you, a recipient and up to six other email addresses of exception and delivery information as it becomes available.

This section represents a log of all technical updates associated with this API and its endpoints. All the changes made are grouped by date. The date mentioned denotes when these changes were loaded into the production. 

To know more about the features, we recommend you visit the API documentation page for this API.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Feb 19, 2024 Change Log:

New Monitoring and intervention (MI), and HealthCare Identifier (HCID) special service options are introduced. The MI special services option can be selected at the shipment level under the shipmentSpecialServices object, and the HCID special services can be selected at the package level under the packageSpecialServices object while creating the shipment request.

Oct 16, 2023 Change Log:

New FedEx Express Domestic services are introduced for EU region. The individual shipments are facilitated with the following service types:

  • FedEx® First
  • FedEx® Priority Express
  • FedEx® Priority
  • FedEx® Priority Express Freight
  • FedEx® Priority Freight

July 17, 2023 Change Log:

The Collect on Delivery (C.O.D) and Electronic Collect on Delivery (E.C.O.D) options are removed for FedEx Express and FedEx Ground services for the U.S. destination shipments. This will be effective from 31st of July, 2023.

The C.O.D and E.C.O.D services remain unaffected for:

  • Intra-Canada shipments
  • FedEx Ground U.S. to Canada shipments
  • Other regions that support C.O.D and E.C.O.D services

Sep 13, 2022 Change Log:

New element emailreturnshipment is added to the Cancel Shipment endpoint.
The element emailreturnshipment value when set boolean true, identifies the shipment as email return shipment and cancels it.

May 22, 2022 Change Log:

Two new label stock types are added as Enumeration values for thermal labels in the labelStockType object:

  • STOCK_4X85_TRAILING_DOC_TAB
  • STOCK_4X105_TRAILING_DOC_TAB

April 22, 2022 Change Log:

New element cargoAircraftOnly is added –
The element cargoAircraftOnly value when set boolean True, specifies cargo aircraft as the mode of shipment transportation for Dangerous Goods. The default value of this element is set to False.
Note: An identifier DGD-CAO is added in AWB for cargo aircraft shipments.

Feb 19, 2022 Change Log:

  • New object soldTo is added to the request:
    The soldTo object will indicate the party responsible for purchasing the goods shipped from the shipper to the recipient. The Sold to party is not necessarily the recipient or the importer of record. The Sold to party is relevant when the purchaser, rather than the recipient determines when certain customs regulations apply.
  • In shipper/contacts object now either personName or companyName is required and not the both. An error will be returned if both personName and CompanyName are blank or not provided in the request.